#24075: Can't migrate contenttypes and auth to zero
-------------------------------------+-------------------------------------
Reporter: apollo13 | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
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 MarkusH):
I'm reverting these patches (https://github.com/django/django/pull/4079)
as they cause more harm (severe impact on test performance (#24251) and
problems in multi-database setups (#24298)) than good. The described error
most likely only occurs on development systems where dropping the
respective tables or the entire database shouldn't be a problem.
This issue can be fixed with #24100 instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/24075#comment:10>
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/066.86298015d7b3533062e772e4aa6bd1fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
