Fixed #3909 -- Added a couple of small clarifications to django-admin.py

documentation. Thanks, adurdin@gmail.com.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@4978 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 4 insertions, 1 deletions

diff --git a/docs/django-admin.txt b/docs/django-admin.txt
index cc23bfb559..52ee823cc3 100644
--- a/docs/django-admin.txt
+++ b/docs/django-admin.txt
@@ -109,7 +109,8 @@ application(s).
 By default, the database will be dumped in JSON format. If you want the output
 to be in another format, use the ``--format`` option (e.g., ``format=xml``).
 You may specify any Django serialization backend (including any user specified
-serialization backends named in the ``SERIALIZATION_MODULES`` setting).
+serialization backends named in the ``SERIALIZATION_MODULES`` setting). The
+``--indent`` option can be used to pretty-print the output.
 
 If no application name is provided, all installed applications will be dumped.
 
@@ -220,6 +221,8 @@ one fixture can reference data in another fixture. If the database backend
 supports row-level constraints, these constraints will be checked at the
 end of the transaction.
 
+The ``dumpdata`` command can be used to generate input for ``loaddata``.
+
 .. admonition:: MySQL and Fixtures
 
     Unfortunately, MySQL isn't capable of completely supporting all the