Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

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
  • Loading branch information...
commit 1c7a264a96da509c74692ba0bc07111f14ee2ff8 1 parent f5d4731
Malcolm Tredinnick authored April 09, 2007

Showing 1 changed file with 4 additions and 1 deletion. Show diff stats Hide diff stats

  1. 5  docs/django-admin.txt
5  docs/django-admin.txt
@@ -109,7 +109,8 @@ application(s).
109 109
 By default, the database will be dumped in JSON format. If you want the output
110 110
 to be in another format, use the ``--format`` option (e.g., ``format=xml``).
111 111
 You may specify any Django serialization backend (including any user specified
112  
-serialization backends named in the ``SERIALIZATION_MODULES`` setting).
  112
+serialization backends named in the ``SERIALIZATION_MODULES`` setting). The
  113
+``--indent`` option can be used to pretty-print the output.
113 114
 
114 115
 If no application name is provided, all installed applications will be dumped.
115 116
 
@@ -220,6 +221,8 @@ one fixture can reference data in another fixture. If the database backend
220 221
 supports row-level constraints, these constraints will be checked at the
221 222
 end of the transaction.
222 223
 
  224
+The ``dumpdata`` command can be used to generate input for ``loaddata``.
  225
+
223 226
 .. admonition:: MySQL and Fixtures
224 227
 
225 228
     Unfortunately, MySQL isn't capable of completely supporting all the

0 notes on commit 1c7a264

Please sign in to comment.
Something went wrong with that request. Please try again.