From 5f7eecd09af8d69722d483b73b5ac3a086ad0e42 Mon Sep 17 00:00:00 2001 From: Ramiro Morales Date: Fri, 1 Feb 2013 21:33:39 -0300 Subject: [PATCH] Small generic FK docs tweaks. --- docs/ref/contrib/contenttypes.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/ref/contrib/contenttypes.txt b/docs/ref/contrib/contenttypes.txt index 34a2fd7f78..fb85653ce8 100644 --- a/docs/ref/contrib/contenttypes.txt +++ b/docs/ref/contrib/contenttypes.txt @@ -277,7 +277,7 @@ A normal :class:`~django.db.models.ForeignKey` can only "point to" one other model, which means that if the ``TaggedItem`` model used a :class:`~django.db.models.ForeignKey` it would have to choose one and only one model to store tags for. The contenttypes -application provides a special field type which +application provides a special field type (``GenericForeignKey``) which works around this and allows the relationship to be with any model: @@ -287,7 +287,8 @@ model: :class:`~django.contrib.contenttypes.generic.GenericForeignKey`: 1. Give your model a :class:`~django.db.models.ForeignKey` - to :class:`~django.contrib.contenttypes.models.ContentType`. + to :class:`~django.contrib.contenttypes.models.ContentType`. The usual + name for this field is "content_type". 2. Give your model a field that can store primary key values from the models you'll be relating to. For most models, this means a