Browse files

Fixed #3774 - primary_key=True does not, in fact, imply blank=False

git-svn-id: http://code.djangoproject.com/svn/django/trunk@7713 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 6123f84 commit 9cf3048b0801aeefd5b5a78ad407b234265d1ffa @spookylukey spookylukey committed Jun 20, 2008
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/model-api.txt
View
4 docs/model-api.txt
@@ -662,8 +662,8 @@ Django will automatically add this field::
Thus, you don't need to set ``primary_key=True`` on any of your fields
unless you want to override the default primary-key behavior.
-``primary_key=True`` implies ``blank=False``, ``null=False`` and
-``unique=True``. Only one primary key is allowed on an object.
+``primary_key=True`` implies ``null=False`` and ``unique=True``. Only
+one primary key is allowed on an object.
``radio_admin``
~~~~~~~~~~~~~~~

0 comments on commit 9cf3048

Please sign in to comment.