Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Look into if modeling data differently in the DB has benefits #1075

Open
helgi opened this issue Sep 15, 2016 · 1 comment
Open

Look into if modeling data differently in the DB has benefits #1075

helgi opened this issue Sep 15, 2016 · 1 comment

Comments

@helgi
Copy link
Contributor

helgi commented Sep 15, 2016

Instead of JSONField consider doing a parent/child model to handle proc type information. (and other nested information). Autoscales model with Autoscale for web and worker records. This will only work in some cases. Might not map to health checks very well given it is a very nested structure.

There are two reasons why I want to see some exploration on this

  1. Do validations outside of the JSON Schema hack and rather utilise built-in validations from Django / DRF or at least function based validations
  2. If swagger (Specify the API using swagger #811) happens (or any auto-generated schema format) then having data concretely described it going to help a lot

This may not be viable at all, or is only viable when dealing with very simple structures, at best when we know it needs to only map down to the level of process type

@Cryptophobia
Copy link
Contributor

This issue was moved to teamhephy/controller#51

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants