#30186: Show applied datetime in showmigrations
-------------------------------------+-------------------------------------
Reporter: Timothy Schilling | Owner: Timothy
| Schilling
Type: New feature | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage: Accepted
showmigrations |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Timothy Schilling):
* status: new => assigned
* owner: nobody => Timothy Schilling
* has_patch: 0 => 1
Old description:
> My idea is to add the applied datetime value to the showmigrations
> command.
>
> I've run into the case where I'm working on a branch that involves a
> number of migrations across various apps, but then have to switch to a
> different branch which has different migrations. It can be troublesome to
> determine which migrations are new and need to be rolled back. I've
> recently started looking at the django_migrations table sorted on the
> applied column to determine which I've run recently. This would make
> switching between branches involving conflicting migrations easier.
>
> There was some brief discussion [https://groups.google.com/forum/#!topic
> /django-developers/yWuVFvOUhy4 here].
>
> I've initially implemented this so that it would only apply to the
> `--list` option with a `--verbosity` of 2 and above. [https://github.com
> /tim-schilling/django/pull/1 Here's what I have so far.] I wasn't sure
> how to handle backporting.
New description:
My idea is to add the applied datetime value to the showmigrations
command.
I've run into the case where I'm working on a branch that involves a
number of migrations across various apps, but then have to switch to a
different branch which has different migrations. It can be troublesome to
determine which migrations are new and need to be rolled back. I've
recently started looking at the django_migrations table sorted on the
applied column to determine which I've run recently. This would make
switching between branches involving conflicting migrations easier.
There was some brief discussion [https://groups.google.com/forum/#!topic
/django-developers/yWuVFvOUhy4 here].
I've initially implemented this so that it would only apply to the
`--list` option with a `--verbosity` of 2 and above. ~~[https://github.com
/tim-schilling/django/pull/1 Here's what I have so far.] I wasn't sure how
to handle backporting.~~
[https://github.com/django/django/pull/10997 PR]
Edited to strikeout old PR and reference the one to origin.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/30186#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.4b5a8ae7dd781a6717e1a685150ada83%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
