#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:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by David Wobrock):
* owner: nobody => David Wobrock
* status: new => assigned
Comment:
Hi! This seems quite relevant to me, as in the company I work for, we'll
probably start using squashed migration soon-ish and we use sqlmigrate
extensively.
I'd like to tackle this change :)
It does not seem too complicated to allowed inspecting the SQL of replaced
migrations.
I already wrote a small test that reproduces the behaviour described in
the stacktrace.
Technically, I guess I should be able to find an elegant way to detect the
migration was replaced and find it in the MigrationLoader.
Visually, should the command display that the inspected migration is
replaced and by which squashed migration?
Thanks!
David
--
Ticket URL: <https://code.djangoproject.com/ticket/31318#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.47609cacfadbacc8e44eb8970332270f%40djangoproject.com.
