Changes between Version 1 and Version 2 of Ticket #29198, comment 3
- Timestamp:
- Apr 14, 2018, 10:30:15 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29198, comment 3
v1 v2 1 I'm very interested in some version of this functionality as well, though my case may be different enough to warrant another ticket. I'd like to see top-level feedback along the lines suggested by Craig in the specific ''and'' general migration case ( ./manage.py migrate and ./manage.py migrate account 0001_initial). I'd also like to be able to run `sqlmigrate` against all pending migrations so that I can easily know the queries that will be run against the DB. I'm not too knowledgeable about Django's migration internals (yet!) but am glad to take a first stab at this functionality!1 I'm very interested in some version of this functionality as well, though my case may be different enough to warrant another ticket. I'd like to see top-level feedback along the lines suggested by Craig in the specific ''and'' general migration case (`./manage.py migrate` and `./manage.py migrate account 0001_initial`). I'd also like to be able to run `sqlmigrate` against all pending migrations so that I can easily know the queries that will be run against the DB. I'm not too knowledgeable about Django's migration internals (yet!) but am glad to take a first stab at this functionality!