Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #12840: mark natural key serialization in the docs as new in 1.…

…2. Thanks, ramiro.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@12432 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 3d849047949c494e10fcb6c1f85fe9b43fd4f478 1 parent 1d078be
Jacob Kaplan-Moss authored February 14, 2010

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

  1. 6  docs/topics/serialization.txt
6  docs/topics/serialization.txt
@@ -196,6 +196,10 @@ them. Something like this will work::
196 196
 Natural keys
197 197
 ------------
198 198
 
  199
+.. versionadded:: 1.2
  200
+   The ability to use natural keys when serializing/deserializing data was
  201
+   added in the 1.2 release.
  202
+
199 203
 The default serialization strategy for foreign keys and many-to-many
200 204
 relations is to serialize the value of the primary key(s) of the
201 205
 objects in the relation. This strategy works well for most types of
@@ -341,7 +345,7 @@ a `forward reference` with natural keys - the data you are referencing
341 345
 must exist before you include a natural key reference to that data.
342 346
 
343 347
 To accommodate this limitation, calls to :djadmin:`dumpdata` that use
344  
-the :djadminopt:`--natural` optionwill serialize any model with a
  348
+the :djadminopt:`--natural` option will serialize any model with a
345 349
 ``natural_key()`` method before it serializes normal key objects.
346 350
 
347 351
 However, this may not always be enough. If your natural key refers to

0 notes on commit 3d84904

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