#27926: Squashmigrations --hard
----------------------------------+--------------------------------------
Reporter: Pascal Briet | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: squashmigrations | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Pascal Briet):
If we think longer term, would it be suitable to have more about the SQL
structure within the models.py files?
We currently consider - my team and I - that models.py is describing the
whole database structure (as we don't need yet views or custom indexes).
May it be a good idea to introduce more concepts in models.py files. e.g.
for views, having somethink like this :
{{{
class MySqlView(models.SqlView):
QUERY = "SELECT * FROM xxx JOIN yyy ON ...."
}}}
and handle the modifications in migrations like the rest? (DROP VIEW &&
CREATE VIEW)
With the following objective : reducing the number of RunSQL migrations,
and make our "hard reset" approach more global.
--
Ticket URL: <https://code.djangoproject.com/ticket/27926#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.3e4ec17e158f103f022da796a4072da9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
