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.


You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to