diff options
| author | Alasdair Nicol <alasdair@thenicols.net> | 2016-09-28 11:50:49 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-09-28 06:51:42 -0400 |
| commit | 6e24eeef602aaadeb371dd57c4e81aeb0750d96d (patch) | |
| tree | 752425c71d8a8d786a5b9e5a15d081e6684b4447 | |
| parent | d5430a5ff992992eae19be63da8818356d315751 (diff) | |
| download | django-6e24eeef602aaadeb371dd57c4e81aeb0750d96d.tar.gz | |
[1.8.x] Fixed 27283 -- Fixed typo in 1.8 release notes.
Backport of 32031718320e1b4d708b15d8c67738e4c77c9bc7 from master
| -rw-r--r-- | docs/releases/1.8.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt index e00c56b38f..083b1d1a8e 100644 --- a/docs/releases/1.8.txt +++ b/docs/releases/1.8.txt @@ -1189,7 +1189,7 @@ Miscellaneous 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 + ``name`` column won't be dropped from the database. Use ``manage.py migrate --fake-initial`` to fake only the initial migration instead. * :djadmin:`migrate` now accepts the :djadminopt:`--fake-initial` option to |