#26760: Delete nonexistent migrations from django_migrations table
-------------------------------------+-------------------------------------
Reporter: jarekwg | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: django_migrations | Triage Stage: Accepted
squash migrations |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
In #26429 we added a timestamp to merge migration names to reduce the
likelihood of collisions there. I acknowledge this could happen in other
situations though.
--
Ticket URL: <https://code.djangoproject.com/ticket/26760#comment:1>
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/065.5db5fecbe20dfcdf753d0d75c6bd7290%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
