Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.9.x] Fixed #25100 -- Documented an upgrade caveat for contenttypes migration.

Browse Source 
Backport of 81b55fb90078788bfdc064550f2ff9da2c79d3b6 from master
This commit is contained in:
Tim Graham 2015-10-29 16:41:26 -04:00
parent 31a51a04e8
commit 8b1c386f80
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/releases/1.8.txt
View File

@ -1181,6 +1181,12 @@ Miscellaneous
has been removed by a migration and replaced by a property. That means it's 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. not possible to query or filter a ``ContentType`` by this field any longer.
Be careful if you upgrade to Django 1.8 and skip Django 1.7. If you run
``manage.py migrate --fake``, this migration will be skipped and you'll see
a ``RuntimeError: Error creating new content types.`` exception because the
``name`` column won't be dropped from the database. Use ``migrate.py migrate
--fake-initial`` to fake only the initial migration instead.
* :djadmin:`migrate` now accepts the :djadminopt:`--fake-initial` option to * :djadmin:`migrate` now accepts the :djadminopt:`--fake-initial` option to
allow faking initial migrations. In 1.7 initial migrations were always allow faking initial migrations. In 1.7 initial migrations were always
automatically faked if all tables created in an initial migration already automatically faked if all tables created in an initial migration already