#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) | Keywords: migrate migrations
Severity: Normal | sqlall
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
When upgrading a django+djangocms install to latest versions, things got
broken (at least one sql table with missing, even though MIGRATION_MODULES
was well filled and "manage.py migrate" indicated all was up-to-date).
I wanted to use sqlall and other commands to diff my existing DB with the
"theoretical" one, but django refused, indicating that only sqlmigrate and
sqlflush were allowed for apps with migrations. I had to redeploy another
install from scratch to do the diff.
Wouldn't it be better to issue a warning in these cases, but let the
developper use these tools to understand what's wrong, and manually "fake"
migrations when stuffs are out of control ?
--
Ticket URL: <https://code.djangoproject.com/ticket/24481>
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/048.b8e2eb73801af828a199471866d6e256%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
