summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-09-05 06:02:28 -0700
committerTim Graham <timograham@gmail.com>2013-09-05 06:02:28 -0700
commitd70908e9c2fda803181ff53f82bf58eaaec22d3e (patch)
tree68eff00846a744f78915f7f70453b585b1e62e4e /docs
parenteacf060e01617ea5e910e8f8a5805483cd5c60b0 (diff)
parentb7af44d474a4394f90248240255d57c3c46e4894 (diff)
Merge pull request #1549 from loic/docs
Removed "makemigrations --force" from docs since it doesn't actually exist.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/migrations.txt11
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/topics/migrations.txt b/docs/topics/migrations.txt
index 136ee79bb4..4ad140c98c 100644
--- a/docs/topics/migrations.txt
+++ b/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: