1
0
mirror of https://github.com/django/django.git synced 2025-07-06 18:59:13 +00:00

Added a note about not using 'pk' as a field name for a non-primary-key field.

git-svn-id: http://code.djangoproject.com/svn/django/branches/queryset-refactor@6114 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-09-13 02:48:06 +00:00
parent 2d07a19c19
commit 4751fd9ba7

View File

@ -1348,6 +1348,11 @@ equivalent::
Entry.objects.filter(blog__id=3) # __exact is implied Entry.objects.filter(blog__id=3) # __exact is implied
Entry.objects.filter(blog__pk=3) # __pk implies __id__exact Entry.objects.filter(blog__pk=3) # __pk implies __id__exact
.. note::
Because of this shortcut, you cannot have a field in your model called
``pk`` that is not the primary key of the model. It will always be
replaced by the name of the model's primary key in queries.
Lookups that span relationships Lookups that span relationships
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~