#24524: Automatic migrations prevent creation of initial database table layout
-------------------------------------+-------------------------------------
Reporter: SimonSteinberger | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 1.8rc1
Severity: Normal | Resolution:
| worksforme
Keywords: migrations, fail, | Triage Stage:
collision | Unreviewed
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
Sorry for the delay jbrendel,
The issue you are hitting with `contrib.sites` is similar to what #22411
was for `contrib.contenttypes` and caused by the fact `pre_migrate`
signals receivers have no way to determine the current state of applied
migrations.
This is an issue that is also blocking #24067 where I initially thought
that dispatching the migration plan (#24100) would expose enough details
to fix it.
Could you provide us the traceback you get when trying to run your test
suite with `./manage.py test -v2`?
--
Ticket URL: <https://code.djangoproject.com/ticket/24524#comment:17>
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/074.341a536c0a3e339deccdf6b6127439a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
