Fixed #7609 -- Noted in the model fields reference documentation that `PositiveIntegerField` accepts the value 0 for backwards-compatibility reasons. Thanks to everyone involved in the resolution of this issue, including Paul Collins for the patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16972 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
c58e5724bc
commit
406f9d1fa0
|
@ -805,7 +805,8 @@ this as a ``<select>`` box with "Unknown", "Yes" and "No" choices.
|
||||||
|
|
||||||
.. class:: PositiveIntegerField([**options])
|
.. class:: PositiveIntegerField([**options])
|
||||||
|
|
||||||
Like an :class:`IntegerField`, but must be positive.
|
Like an :class:`IntegerField`, but must be either positive or zero (`0`).
|
||||||
|
The value `0` is accepted for backward compatibility reasons.
|
||||||
|
|
||||||
``PositiveSmallIntegerField``
|
``PositiveSmallIntegerField``
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
Loading…
Reference in New Issue