#35363 closed New feature (wontfix)
Makemigrations: option to "depend on most current everything"
| Reported by: | Klaas van Schelven | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 5.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (2)
comment:1 by , 6 weeks ago
| Component: | Uncategorized → Migrations |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
| Type: | Uncategorized → New feature |
Note:
See TracTickets
for help on using tickets.
Hi Klaas,
This sounds like a feature request? In this case the recommended path forward is to first propose and discuss the idea with the community and gain consensus. To do that, please consider starting a new conversation on the Django Forum, where you'll reach a much wider audience and likely get extra feedback.
I'll close the ticket for now, but if there is a community agreement that this is needed, you are welcome to come back to the ticket and point to the forum topic, so we can then re-open it. For more details, please see the documented guidelines for requesting features.
Thank you!