#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 Natalia Bidart):
Replying to [comment:5 Jacob Walls]:
> > as long as one doesn't delete the original migrations when doing the
squashing.
>
> Sorry, I took that to be part of the point of the proposal, but it looks
like that was an assumption on my part.
I did assume that the original migrations would not be deleted. But, my
thinking when mentioning breakages was more related to: when new `auth`
migrations need to be added, which migration would these new files depend
on? the latest non-squashed? the squashed one? As far as I understand
either answer breaks "the other case" (our docs are not that explicit
about a case similar to this).
Because of the impact that this can (potentially) have, I think that, if
we want to consider re-opening, we need a forum discussion with some
general agreement that this is both:
* desired, and
* does not break current or future Django projects.
--
Ticket URL: <https://code.djangoproject.com/ticket/35707#comment:6>
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/0107019196be4de5-3f8c83cf-4999-42b2-8775-46398e7cdcff-000000%40eu-central-1.amazonses.com.
