#31318: sqlmigrate doesn't allow inspecting migrations that have been squashed
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: David
Johnson | Wobrock
Type: | Status: assigned
Cleanup/optimization |
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam (Chainz) Johnson):
Sorry didn't see your comment until now, went through my spam box.
> Visually, should the command display that the inspected migration is
replaced and by which squashed migration?
I don't think that's necessary. The recommended procedure with a squashed
migration is to drop the originals after every developer and deployment
has received the squashed one. So the state where both exist in parallel
doesn't live for long.
--
Ticket URL: <https://code.djangoproject.com/ticket/31318#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/068.58c556adc018cef80d75946af9855846%40djangoproject.com.
