diff options
| author | Markus Holtermann <info@markusholtermann.eu> | 2015-02-12 12:48:28 +0100 |
|---|---|---|
| committer | Markus Holtermann <info@markusholtermann.eu> | 2015-02-13 14:29:59 +0100 |
| commit | f287bec5833d75750fa6368bc2802741b7924533 (patch) | |
| tree | 9ab7db3bc9a1834ead7366c0062b9fb39f457648 /docs/releases | |
| parent | b4e1090ab28c0e731157a61a91a6875bad392307 (diff) | |
Fixed #24184 -- Prevented automatic soft-apply of migrations
Previously Django only checked for the table name in CreateModel
operations in initial migrations and faked the migration automatically.
This led to various errors and unexpected behavior. The newly introduced
--fake-initial flag to the migrate command must be passed to get the
same behavior again. With this change Django will bail out in with a
"duplicate relation / table" error instead.
Thanks Carl Meyer and Tim Graham for the documentation update, report
and review.
Diffstat (limited to 'docs/releases')
| -rw-r--r-- | docs/releases/1.8.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index 4f77f063a3..4c7076a51e 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -1135,6 +1135,11 @@ Miscellaneous has been removed by a migration and replaced by a property. That means it's not possible to query or filter a ``ContentType`` by this field any longer. +* :djadmin:`migrate` now accepts the :djadminopt:`--fake-initial` option to + allow faking initial migrations. In 1.7 initial migrations were always + automatically faked if all tables created in an initial migration already + existed. + .. _deprecated-features-1.8: Features deprecated in 1.8 |