[Django] #35363: Makemigrations: option to "depend on most current everything"

[Django]

#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.

[Django]

#35363: Makemigrations: option to "depend on most current everything"

------------------------------------+--------------------------------------

Reporter: Klaas van Schelven | Owner: nobody

Type: New feature | Status: closed
Component: Migrations | Version: 5.0
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

------------------------------------+--------------------------------------
Changes (by Sarah Boyce):

* component: Uncategorized => Migrations
* resolution: => wontfix
* status: new => closed
* type: Uncategorized => New feature

Comment:

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 [https://forum.djangoproject.com/c/internals/5 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
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features].

Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/35363#comment:1>

[Django]

#35363: Makemigrations: option to "depend on most current everything"
------------------------------------+--------------------------------------
Reporter: Klaas van Schelven | Owner: nobody
Type: New feature | Status: closed
Component: Migrations | Version: 5.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------

Comment (by Klaas van Schelven):

https://forum.djangoproject.com/t/makemigrations-option-to-depend-on-most-
current-everything/29989
--
Ticket URL: <https://code.djangoproject.com/ticket/35363#comment:2>