Fixed spaces vs. tabs issue in docs/contenttypes.txt from [7976]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8042 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
46c7941de3
commit
ca98003390
|
@ -205,10 +205,10 @@ model. There are three parts to setting up a ``GenericForeignKey``:
|
|||
models you'll be relating to. (For most models, this means an
|
||||
``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.
|
||||
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
|
||||
the two fields described above. If these fields are named
|
||||
|
|
Loading…
Reference in New Issue