From 9cf3048b0801aeefd5b5a78ad407b234265d1ffa Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Fri, 20 Jun 2008 12:10:13 +0000 Subject: [PATCH] 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 --- docs/model-api.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/model-api.txt b/docs/model-api.txt index 93c2a34399..89f5ffb812 100644 --- a/docs/model-api.txt +++ b/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`` ~~~~~~~~~~~~~~~