diff options
| author | Ian Kelly <ian.g.kelly@gmail.com> | 2009-03-05 20:22:54 +0000 |
|---|---|---|
| committer | Ian Kelly <ian.g.kelly@gmail.com> | 2009-03-05 20:22:54 +0000 |
| commit | de442c3ab69e4b982694591384b7114c65f16dc6 (patch) | |
| tree | 7b4e226b23a3de613def10bcc9bf443d174ca782 /docs/ref/models | |
| parent | 79f53b4f206f82847b645e36263e3537ebbae7b1 (diff) | |
[1.0.X] Clarified documentation regarding Oracle's treatment of nulls and empty strings. Backport of [9976] from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9977 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/fields.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 63018f6611..4643837841 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -54,8 +54,8 @@ string, not ``NULL``. .. note:: When using the Oracle database backend, the ``null=True`` option will be - coerced for string-based fields that can blank, and the value ``NULL`` will - be stored to denote the empty string. + coerced for string-based fields that have the empty string as a possible + value, and the value ``NULL`` will be stored to denote the empty string. ``blank`` --------- |