[4.0.x] Fixed #22224 -- Added note about supplying missing values for non-nullable fields with blank=True.
Backport of cd6bddd44e
from main
This commit is contained in:
parent
816e809302
commit
515d3c591c
|
@ -73,6 +73,12 @@ purely database-related, whereas :attr:`~Field.blank` is validation-related. If
|
||||||
a field has ``blank=True``, form validation will allow entry of an empty value.
|
a field has ``blank=True``, form validation will allow entry of an empty value.
|
||||||
If a field has ``blank=False``, the field will be required.
|
If a field has ``blank=False``, the field will be required.
|
||||||
|
|
||||||
|
.. admonition:: Supplying missing values
|
||||||
|
|
||||||
|
``blank=True`` can be used with fields having ``null=False``, but this will
|
||||||
|
require implementing :meth:`~django.db.models.Model.clean` on the model in
|
||||||
|
order to programmatically supply any missing values.
|
||||||
|
|
||||||
.. _field-choices:
|
.. _field-choices:
|
||||||
|
|
||||||
``choices``
|
``choices``
|
||||||
|
|
Loading…
Reference in New Issue