#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):
I see, the code that makes sure to create a default site assumes that the
`Site`'s table exist after each `migrate` even if the migrations to apply
were restricted to a subset that don't include the initial `sites`
migration.
--
Ticket URL: <https://code.djangoproject.com/ticket/24524#comment:14>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.d2e9a1ef783969ed7de1b7df2481b389%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
