#35363: Makemigrations: option to "depend on most current everything"
----------------------------------------------+------------------------
Reporter: Klaas van Schelven | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 5.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------------+------------------------
The order in which Django migrations are run is determined when running
migrate as any of a number of legal orderings of a DAG. I understand why
that this is a useful feature... however: it does generate a source of
non-determinism that may come back to bite you when you least expect it
(e.g. when rolling out to production).
In many cases I would be fine to specify a migration to have exactly the
dependencies that are observable as the exiting per-app last migrations at
the moment of creating the migration. It would be nice if there was an
option to makemigrations that just dumped all existing such info into the
dependencies field.
--
Ticket URL: <https://code.djangoproject.com/ticket/35363>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ec20eee49-54b0cc2b-f24f-4fb5-a73f-6bfe7b5f7ed9-000000%40eu-central-1.amazonses.com.
