mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00
Code Issues 32 Releases Wiki Activity

Removed docs about unmigrated apps as they are not supported in Django 1.9.

Browse Source
This commit is contained in:
Tim Graham
2015-02-09 10:28:42 -05:00
parent 2d7c27d387
commit c5d1a5ef5c
3 changed files with 1 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/topics/migrations.txt
View File

@@ -24,11 +24,6 @@ and Django's handling of database schema:
* :djadmin:`sqlmigrate`, which displays the SQL statements for a migration.
It's worth noting that migrations are created and run on a per-app basis.
In particular, it's possible to have apps that *do not use migrations* (these
are referred to as "unmigrated" apps) - these apps will instead mimic the
legacy behavior of just adding new models.
You should think of migrations as a version control system for your database
schema. ``makemigrations`` is responsible for packaging up your model changes
into individual migration files - analogous to commits - and ``migrate`` is
@@ -139,9 +134,6 @@ database to make sure they work as expected::
Rendering model states... DONE
Applying books.0003_auto... OK
The command runs in two stages; first, it synchronizes unmigrated apps, and
then it runs any migrations that have not yet been applied.
Once the migration is applied, commit the migration and the models change
to your version control system as a single commit - that way, when other
developers (or your production servers) check out the code, they'll