Fixed #17511 - Removed reference to deprecated "reset" management command in FAQ; thanks voxpuibr@ for the report.
This commit is contained in:
parent
1cf8287e3a
commit
c8928b91b5
|
@ -40,18 +40,15 @@ Yes. See :doc:`Integrating with a legacy database </howto/legacy-databases>`.
|
||||||
If I make changes to a model, how do I update the database?
|
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
|
If you don't mind clearing data, your project's ``manage.py`` utility has a
|
||||||
option to reset the SQL for a particular application::
|
:djadmin:`flush` option to reset the database to the state it was in
|
||||||
|
immediately after :djadmin:`syncdb` was executed.
|
||||||
manage.py reset appname
|
|
||||||
|
|
||||||
This drops any tables associated with ``appname`` and recreates them.
|
|
||||||
|
|
||||||
If you do care about deleting data, you'll have to execute the ``ALTER TABLE``
|
If you do care about deleting data, you'll have to execute the ``ALTER TABLE``
|
||||||
statements manually in your database.
|
statements manually in your database.
|
||||||
|
|
||||||
There are `external projects which handle schema updates
|
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/>`_.
|
defacto standard is `south <http://south.aeracode.org/>`_.
|
||||||
|
|
||||||
Do Django models support multiple-column primary keys?
|
Do Django models support multiple-column primary keys?
|
||||||
|
|
|
@ -224,8 +224,8 @@ flush
|
||||||
|
|
||||||
.. django-admin:: flush
|
.. django-admin:: flush
|
||||||
|
|
||||||
Returns the database to the state it was in immediately after syncdb was
|
Returns the database to the state it was in immediately after :djadmin:`syncdb`
|
||||||
executed. This means that all data will be removed from the database, any
|
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``
|
post-synchronization handlers will be re-executed, and the ``initial_data``
|
||||||
fixture will be re-installed.
|
fixture will be re-installed.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue