Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

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

…exist.
  • Loading branch information...
commit b7af44d474a4394f90248240255d57c3c46e4894 1 parent 34d52fd
Loic Bistuer authored September 05, 2013

Showing 1 changed file with 5 additions and 6 deletions. Show diff stats Hide diff stats

  1. 11  docs/topics/migrations.txt
11  docs/topics/migrations.txt
@@ -255,13 +255,12 @@ If your app already has models and database tables, and doesn't have migrations
255 255
 yet (for example, you created it against a previous Django version), you'll
256 256
 need to convert it to use migrations; this is a simple process::
257 257
 
258  
-    python manage.py makemigrations --force yourappname
  258
+    python manage.py makemigrations yourappname
259 259
 
260  
-This will make a new initial migration for your app (the ``--force`` argument
261  
-is to override Django's default behaviour, as it thinks your app does not want
262  
-migrations). Now, when you run :djadmin:`migrate`, Django will detect that
263  
-you have an initial migration *and* that the tables it wants to create already
264  
-exist, and will mark the migration as already applied.
  260
+This will make a new initial migration for your app. Now, when you run
  261
+:djadmin:`migrate`, Django will detect that you have an initial migration
  262
+*and* that the tables it wants to create already exist, and will mark the
  263
+migration as already applied.
265 264
 
266 265
 Note that this only works given two things:
267 266
 

0 notes on commit b7af44d

Please sign in to comment.
Something went wrong with that request. Please try again.