#24572: Migration plan may be broken when applying migrations on a clean
database
----------------------------+------------------------------------
Reporter: MarkusH | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by MarkusH):
Actually it is bbbed99f6260a8b3e65cb990e49721b1ce4a441b. Which also makes
way more sense, as this does use `a.2` to generate the initial state right
before each migration that needs to be applied. See
https://github.com/django/django/blob/3e7d9d05ac5efff4e4732c3453c7a8ef502d0ed0/django/db/migrations/executor.py#L65
for details.
--
Ticket URL: <https://code.djangoproject.com/ticket/24572#comment:3>
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/065.c7b4ace2c2f2ece1c5b541d623a9d068%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
