#25304: Allow management commands to check if database migrations are applied
-------------------------------------+-------------------------------------
Reporter: mlorant | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: 1.8
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
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: 1 => 0
* component: contrib.auth => Core (Management commands)
* easy: 1 => 0
* has_patch: 1 => 0
* type: Cleanup/optimization => New feature
* stage: Unreviewed => Accepted
Comment:
I don't think the exception catching solution would work perfectly. For
example, there's no guarantee that the database exception is due to
missing tables and not some other bad query, etc. A more viable solution
might be to allow management commands to check if all database migrations
are applied and to output a warning if not, similar to what `runserver`
does. Accepting the ticket for investigation of that idea. #24484 is
similar.
--
Ticket URL: <https://code.djangoproject.com/ticket/25304#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 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/065.8bc0138f4407af63d6442d983553d0d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
