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
This commit is contained in:
parent
6123f8455c
commit
9cf3048b08
|
@ -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``
|
||||
~~~~~~~~~~~~~~~
|
||||
|
|
Loading…
Reference in New Issue