Ticket #19115: 19115.patch

django/core/management/commands/dumpdata.py

@@ -8 +8 @@
 
 class Command(BaseCommand):
     option_list = BaseCommand.option_list + (
+        make_option('-o', '--out', default=None, dest='out',
+                    help='File for dump data. Default to `stdout`'),
         make_option('--format', default='json', dest='format',
             help='Specifies the output serialization format for fixtures.'),
         make_option('--indent', default=None, dest='indent', type='int',
@@ -37 +39 @@
         show_traceback = options.get('traceback')
         use_natural_keys = options.get('use_natural_keys')
         use_base_manager = options.get('use_base_manager')
+        out = options.get('out')
 
         excluded_apps = set()
         excluded_models = set()
@@ -111 +114 @@
                             order_by(model._meta.pk.name).iterator():
                         yield obj
 
+        def dump(out):
+            serializers.serialize(format, get_objects(), indent=indent,
+                                  use_natural_keys=use_natural_keys,
+                                  stream=out)
+
         try:
             self.stdout.ending = None
-            serializers.serialize(format, get_objects(), indent=indent,
-                    use_natural_keys=use_natural_keys, stream=self.stdout)
+            if out:
+                with open(out, 'w') as outfile:
+                    dump(outfile)
+            else:
+                dump(self.stdout)
         except Exception as e:
             if show_traceback:
                 raise

docs/ref/django-admin.txt

@@ -183 +183 @@
 ``dumpdata`` should use Django's base manager, dumping records which
 might otherwise be filtered or modified by a custom manager.
 
+.. versionadded:: 1.6
+
+.. django-admin-option:: --out <filepath>
+
+By default, ``dumpdata`` sends dumped data to ``stdout``, but you can save it into file.
+If file is exists, it be is rewritten.
+
 .. django-admin-option:: --format <fmt>
 
 By default, ``dumpdata`` will format its output in JSON, but you can use the

tests/regressiontests/fixtures_regress/tests.py

@@ -2 +2 @@
 # Unittests for fixtures.
 from __future__ import absolute_import, unicode_literals
 
+from tempfile import NamedTemporaryFile
 import os
 import re
 
@@ -362 +363 @@
             % widget.pk
             )
 
+    def test_dumpdata_with_to_stdout(self):
+        stdout = StringIO()
+        management.call_command(
+            'dumpdata',
+            'fixtures_regress.widget',
+            stdout=stdout
+        )
+        self.assertTrue(stdout.getvalue())
+
+    def test_dumpdata_out_to_file(self):
+        stdout = StringIO()
+        with NamedTemporaryFile() as tmpfile:
+            management.call_command(
+                'dumpdata',
+                'fixtures_regress.widget',
+                format='json',
+                out=tmpfile.name,
+                stdout=stdout
+            )
+            self.assertFalse(stdout.getvalue())
+            self.assertTrue(tmpfile.read())
+
     def test_loaddata_works_when_fixture_has_forward_refs(self):
         """
         Regression for #3615 - Forward references cause fixtures not to load in MySQL (InnoDB)