id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 13418,"Natural keys documentation: 1) tuple requirement in serialization is missing, 2) use unique_together",hunajakippo,nobody,"As discussed {1} I propose following changes to natural keys (de)serialization documentation {2}: 1) mention requirement to use tuple also in natural keys/serialization section (currently this is only mentioned in deserialization). * For example: ""A natural key is a tuple of values that can be used to uniquely identify an object instance without using the primary key value"" 2) in the example model define Person first_name and last_name as unique_together. * For example: ""class Meta: unique_together = ((""first_name"", ""last_name""),)"" {1} http://groups.google.com/group/django-users/browse_thread/thread/2d2aed5d45d48a94 {2} http://docs.djangoproject.com/en/dev/topics/serialization/#natural-keys",,closed,Documentation,dev,,fixed,,,Ready for checkin,1,0,0,0,0,0