Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Clarified documentation regarding Oracle's treatment of nulls and emp…

…ty strings.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9976 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit ad6ce1e6f99a6427a4c01a175d72f21cd28f816a 1 parent 7197a4d
Ian Kelly ikelly authored
Showing with 9 additions and 8 deletions.
  1. +7 −6 docs/ref/databases.txt
  2. +2 −2 docs/ref/models/fields.txt
13 docs/ref/databases.txt
View
@@ -475,12 +475,13 @@ characters of the truncated name with a repeatable MD5 hash value.
NULL and empty strings
----------------------
-Django generally prefers to use the empty string ('') rather than NULL, but
-Oracle treats both identically. To get around this, the Oracle backend
-coerces the ``null=True`` option on fields that permit the empty string as a
-value. When fetching from the database, it is assumed that a NULL value in
-one of these fields really means the empty string, and the data is silently
-converted to reflect this assumption.
+Django generally prefers to use the empty string ('') rather than
+NULL, but Oracle treats both identically. To get around this, the
+Oracle backend coerces the ``null=True`` option on fields that have
+the empty string as a possible value. When fetching from the database,
+it is assumed that a NULL value in one of these fields really means
+the empty string, and the data is silently converted to reflect this
+assumption.
``TextField`` limitations
-------------------------
4 docs/ref/models/fields.txt
View
@@ -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``
---------
Please sign in to comment.
Something went wrong with that request. Please try again.