From 77ec8ae811f0f9d6a55c570ee7c02c52e6e7bc8d Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Tue, 8 May 2007 03:20:49 +0000 Subject: [PATCH] Fixed #4203 -- Noted that "blank" defaults to False in models. Thanks, david@kazserve.org. git-svn-id: http://code.djangoproject.com/svn/django/trunk@5166 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- AUTHORS | 1 + docs/model-api.txt | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/AUTHORS b/AUTHORS index dfa7eb615a0..4fd8540b2f9 100644 --- a/AUTHORS +++ b/AUTHORS @@ -50,6 +50,7 @@ answer newbie questions, and generally made Django that much better: Fabrice Aneche ant9000@netwise.it David Ascher + david@kazserve.org Arthur axiak@mit.edu Jiri Barton diff --git a/docs/model-api.txt b/docs/model-api.txt index a14c4696618..961269aebdd 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -459,7 +459,7 @@ string, not ``NULL``. ``blank`` ~~~~~~~~~ -If ``True``, the field is allowed to be blank. +If ``True``, the field is allowed to be blank. Default is ``False``. Note that this is different than ``null``. ``null`` is purely database-related, whereas ``blank`` is validation-related. If a field has