#28250: migration depending on non-existing legacy migration
-------------------------------+------------------------------------------
Reporter: Brian May | Owner: Marten Kenbeek
Type: Uncategorized | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------------
Comment (by Raphaël Hertzog):
Replying to [comment:12 Marten Kenbeek]:
> That seems to be because the project state generated for the
`pre_migrate` signal only includes state changes of migrations that are
applied. Since the initial migration is still marked as not applied, its
state changes are not propagated to the project state. I've updated the PR
to fix this issue as well.
Thanks! I got the confirmation that the upgrade is now working fine with
the last version of your pull request. It would be great to get this
merged and backported to 1.10 and 1.11.
The backport for 1.10 that I'm using is available in
https://github.com/rhertzog/django/commits/ticket_28250
--
Ticket URL: <https://code.djangoproject.com/ticket/28250#comment:13>
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/063.730618ce34e01f7a6b9a04557b650de8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
