Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Removed "makemigrations --force" from docs since it doesn't actually …

…exist.
  • Loading branch information...
commit b7af44d474a4394f90248240255d57c3c46e4894 1 parent 34d52fd
@loic loic authored
Showing with 5 additions and 6 deletions.
  1. +5 −6 docs/topics/migrations.txt
View
11 docs/topics/migrations.txt
@@ -255,13 +255,12 @@ If your app already has models and database tables, and doesn't have migrations
yet (for example, you created it against a previous Django version), you'll
need to convert it to use migrations; this is a simple process::
- python manage.py makemigrations --force yourappname
+ python manage.py makemigrations yourappname
-This will make a new initial migration for your app (the ``--force`` argument
-is to override Django's default behaviour, as it thinks your app does not want
-migrations). Now, when you run :djadmin:`migrate`, Django will detect that
-you have an initial migration *and* that the tables it wants to create already
-exist, and will mark the migration as already applied.
+This will make a new initial migration for your app. Now, when you run
+:djadmin:`migrate`, Django will detect that you have an initial migration
+*and* that the tables it wants to create already exist, and will mark the
+migration as already applied.
Note that this only works given two things:
Please sign in to comment.
Something went wrong with that request. Please try again.