p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #8693: Fixed formatting of the "null" argument for model fields 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8737 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2008-08-30 05:38:07 +00:00
parent ac418c979f
commit 5f3a182357
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/topics/db/models.txt
View File

@ -143,6 +143,7 @@ optional. They're fully explained in the :ref:`reference
ones: ones:
:attr:`~Field.null` :attr:`~Field.null`
If ``True``, Django will store empty values as ``NULL`` in the database. If ``True``, Django will store empty values as ``NULL`` in the database.
Default is ``False``. Default is ``False``.
@ -744,4 +745,4 @@ bindings. This is for the sake of consistency and sanity.)
A final note: If all you want to do is a custom ``WHERE`` clause, you can use A final note: If all you want to do is a custom ``WHERE`` clause, you can use
the :meth:`~QuerySet.extra` lookup method, which lets you add custom SQL to a the :meth:`~QuerySet.extra` lookup method, which lets you add custom SQL to a
query. query.