#35707: Squash migrations in django.contrib.auth for better performance and
nicer
output
-------------------------------------+-------------------------------------
Reporter: Tim Abbott | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: 5.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Klaas van Schelven):
Oh and I've actually tested the above assertion regarding "what happens
with migration 0013?" i.e. when experimenting with this myself I found
that Django depends on the replacing migration, and that databases through
either path (straight through the replacing migration, or the longer
original path) will migrate to the new endpoint as promised.
--
Ticket URL: <https://code.djangoproject.com/ticket/35707#comment:8>
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/01070194cdaece69-b409365d-c690-482f-b7e7-42a6acf413eb-000000%40eu-central-1.amazonses.com.
