1
0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00

Fixed #23410 -- Avoided unnecessary rollbacks in related apps when migrating backwards.

This commit is contained in:
Carl Meyer
2014-11-17 10:13:47 -07:00
parent e7b9a58b08
commit ab2819aa7b
4 changed files with 114 additions and 11 deletions

View File

@@ -737,10 +737,11 @@ The behavior of this command changes depending on the arguments provided:
* ``<app_label>``: The specified app has its migrations run, up to the most
recent migration. This may involve running other apps' migrations too, due
to dependencies.
* ``<app_label> <migrationname>``: Brings the database schema to a state where it
would have just run the given migration, but no further - this may involve
unapplying migrations if you have previously migrated past the named
migration. Use the name ``zero`` to unapply all migrations for an app.
* ``<app_label> <migrationname>``: Brings the database schema to a state where
the named migration is applied, but no later migrations in the same app are
applied. This may involve unapplying migrations if you have previously
migrated past the named migration. Use the name ``zero`` to unapply all
migrations for an app.
Unlike ``syncdb``, this command does not prompt you to create a superuser if
one doesn't exist (assuming you are using :mod:`django.contrib.auth`). Use

View File

@@ -68,3 +68,6 @@ Bugfixes
* Made :class:`~django.db.migrations.operations.RenameModel` reversible
(:ticket:`22248`)
* Avoided unnecessary rollbacks of migrations from other apps when migrating
backwards (:ticket:`23410`).