p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #7785 -- Added a note in the contenttypes documentation that GenericRelations must share a common field type for primary keys. Thanks to Rudolph for the suggestion and initial draft. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@7976 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2008-07-19 02:46:12 +00:00
parent 825622d912
commit b5b0febc4c
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/contenttypes.txt
View File

@ -205,6 +205,11 @@ model. There are three parts to setting up a ``GenericForeignKey``:
models you'll be relating to. (For most models, this means an models you'll be relating to. (For most models, this means an
``IntegerField`` or ``PositiveIntegerField``.) ``IntegerField`` or ``PositiveIntegerField``.)
This field must be of the same type as the primary key of the models
that will be involved in the generic relation. For example, if you use
``IntegerField``, you won't be able to form a generic relation with a
model that uses a ``CharField`` as a primary key.
3. Give your model a ``GenericForeignKey``, and pass it the names of 3. Give your model a ``GenericForeignKey``, and pass it the names of
the two fields described above. If these fields are named the two fields described above. If these fields are named
"content_type" and "object_id", you can omit this -- those are the "content_type" and "object_id", you can omit this -- those are the