#27100: The pre-migration state used to generate the `AppConfig` exposed through
the `pre_migrate` signal should include already applied migration changes
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: 1.10
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"0def695e3cbaa9ede9ae4040a24cfed7417f9065" 0def695e]:
{{{#!CommitTicketReference repository=""
revision="0def695e3cbaa9ede9ae4040a24cfed7417f9065"
Refs #27100 -- Removed obsolete message from tutorial and migrations
topic.
The project state is cached, so when it was calculated in #27100
during the pre-migrate stage, it was no longer calculated on forward
migrations. Backward migrations still calculate it.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27100#comment:6>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019b48ce829f-9f413da8-d1bc-49dc-97ae-63d880aef83f-000000%40eu-central-1.amazonses.com.
