diff --git a/docs/ref/contrib/contenttypes.txt b/docs/ref/contrib/contenttypes.txt index ef857984df..b9610c3abc 100644 --- a/docs/ref/contrib/contenttypes.txt +++ b/docs/ref/contrib/contenttypes.txt @@ -334,7 +334,8 @@ model: generic relations, you should probably be using a natural key to uniquely identify related :class:`~django.contrib.contenttypes.models.ContentType` objects. See :ref:`natural keys` and - :djadminopt:`dumpdata --natural <--natural>` for more information. + :djadminopt:`dumpdata --natural-foreign <--natural-foreign>` for more + information. This will enable an API similar to the one used for a normal :class:`~django.db.models.ForeignKey`; diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index 570766f18d..c6031b7d63 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -1925,14 +1925,14 @@ with ``True`` or ``False``, as you can see with the ``interactive`` option above Named arguments can be passed by using either one of the following syntaxes:: # Similar to the command line - management.call_command('dumpdata', '--natural') + management.call_command('dumpdata', '--natural-foreign') # Named argument similar to the command line minus the initial dashes and # with internal dashes replaced by underscores - management.call_command('dumpdata', natural=True) + management.call_command('dumpdata', natural_foreign=True) - # `use_natural_keys` is the option destination variable - management.call_command('dumpdata', use_natural_keys=True) + # `use_natural_foreign_keys` is the option destination variable + management.call_command('dumpdata', use_natural_foreign_keys=True) .. versionchanged:: 1.8