[1.4.X] Fixed #17511 - Removed reference to deprecated "reset" management...

If I make changes to a model, how do I update the database?

-----------------------------------------------------------

If you don't mind clearing data, your project's ``manage.py`` utility has an

option to reset the SQL for a particular application::

    manage.py reset appname

This drops any tables associated with ``appname`` and recreates them.

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://djangopackages.com/grids/g/database-migration/>`_, of which the current

<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?

.. django-admin:: flush

Returns the database to the state it was in immediately after syncdb was

executed. This means that all data will be removed from the database, any

Returns the database to the state it was in immediately after :djadmin:`syncdb`

was executed. This means that all data will be removed from the database, any

post-synchronization handlers will be re-executed, and the ``initial_data``

fixture will be re-installed.