  
          birthdate = models.DateField()
  
      class Book(models.Model):
          name = models.CharField(max_length=100)
          author = models.ForeignKey(Person)
  
  Ordinarily, serialized data for ``Book`` would use an integer to refer to
 
</s> remove Deserialization of natural keys
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It is for these reasons that Django provides `natural keys`. A natural
 </s> add It is for these reasons that Django provides *natural keys*. A natural </s> remove Then, when you call ``serializers.serialize()``, you provide a
``use_natural_keys=True`` argument::
 </s> add         class Meta:
            unique_together = (('first_name', 'last_name'),)

That method should always return a natural key tuple -- in this
example, ``(first name, last name)``. Then, when you call
``serializers.serialize()``, you provide a ``use_natural_keys=True``
argument::
        class Meta:
            unique_together = (('first_name', 'last_name'),)

  
          birthdate = models.DateField()
  
        class Meta:
            unique_together = (('first_name', 'last_name'),)

      class Book(models.Model):
          name = models.CharField(max_length=100)
          author = models.ForeignKey(Person)
  
  Ordinarily, serialized data for ``Book`` would use an integer to refer to
keep keep add keep keep keep keep keep
 Fixed #13418 -- Added notes on uniqueness requirements for natural keys. Thanks to hunajakippo for the suggestion, and Ramiro Morales for the draft text.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13146 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/topics/serialization.txt