#24481: Allow use of sql* commands even on apps with migrations
-------------------------------------+-------------------------------------
Reporter: pakal | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version: 1.7
commands) |
Severity: Normal | Resolution:
Keywords: migrate migrations | Triage Stage:
sqlall | Unreviewed
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
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think those commands can't work like they did before because when there
are multiple migrations, I don't think it's feasible to determine what the
resulting database schema will look like.
Maybe an idea would be to make the `migration_name` argument to
`sqlmigrate` optional so that you could do `sqlmigrate <app_name>` to get
the SQL for all of your migrations in an app. I guess we might be able to
make `app_name` optional as well so that `sqlmigrate` could easily output
the SQL for all migrations of all apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/24481#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.72a637c6a4f165cf1a019d46e025bf9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
