#13418: Natural keys documentation: 1) tuple requirement in serialization is
missing, 2) use unique_together
---------------------------+------------------------------------------------
Reporter: hunajakippo | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: SVN
Keywords: | Stage: Unreviewed
Has_patch: 0 |
---------------------------+------------------------------------------------
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
--
Ticket URL: <http://code.djangoproject.com/ticket/13418>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
