mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 10:34:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Removed the syncdb command per deprecation timeline.

Browse source
This commit is contained in:
Tim Graham 2014-12-26 12:34:26 -05:00
parent f4f24d30e0
commit f6463bb380
12 changed files with 14 additions and 89 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/topics/migrations.txt
View file

@ -12,17 +12,6 @@ Migrations are Django's way of propagating changes you make to your models
designed to be mostly automatic, but you'll need to know when to make
migrations, when to run them, and the common problems you might run into.
A Brief History
---------------
Prior to version 1.7, Django only supported adding new models to the
database; it was not possible to alter or remove existing models via the
``syncdb`` command (the predecessor to :djadmin:`migrate`).
Third-party tools, most notably `South <http://south.aeracode.org>`_,
provided support for these additional types of change, but it was considered
important enough that support was brought into core Django.
The Commands
------------
@ -157,8 +146,7 @@ database to make sure they work as expected::
Running migrations:
Applying books.0003_auto... OK
The command runs in two stages; first, it synchronizes unmigrated apps
(performing the same functionality that ``syncdb`` used to provide), and
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