#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 Tim Abbott):
Thanks for investigating!
> this will impose a breaking change on users who have explicit
dependencies on these migrations in their own migration files
Hmm, I wasn't aware of any breaking change concern with squashing
migrations, as long as one doesn't delete the original migrations when
doing the squashing. I'll see if I can find time to start a proper Django
forum discussion.
--
Ticket URL: <https://code.djangoproject.com/ticket/35707#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701919590ccb8-cd429071-4f44-4a66-ab12-52c7bc58e75f-000000%40eu-central-1.amazonses.com.
