p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #21031 -- Updated schema migrations FAQ. 

Thanks ramiro for the report.
This commit is contained in:
Tim Graham 2013-10-01 10:39:03 -04:00
parent b66a51ad54
commit 32e40bbe71
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/faq/models.txt
View File

@ -40,17 +40,13 @@ Yes. See :doc:`Integrating with a legacy database </howto/legacy-databases>`.
If I make changes to a model, how do I update the database?
-----------------------------------------------------------
Take a look at Django's support for :mod:`schema migrations
<django.db.migrations>`.
If you don't mind clearing data, your project's ``manage.py`` utility has a
:djadmin:`flush` option to reset the database to the state it was in
immediately after :djadmin:`syncdb` was executed.
If you do care about deleting data, you'll have to execute the ``ALTER TABLE``
statements manually in your database.
There are `external projects which handle schema updates
<http://www.djangopackages.com/grids/g/database-migration/>`_, of which the current
defacto standard is `south <http://south.aeracode.org/>`_.
Do Django models support multiple-column primary keys?
------------------------------------------------------