#22224: Non-nullable blank string-based model field validation doesn't prevent
or
clean `None`
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: closed
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"515d3c591cc65c77b8d46391d15ded576b037d85" 515d3c59]:
{{{
#!CommitTicketReference repository=""
revision="515d3c591cc65c77b8d46391d15ded576b037d85"
[4.0.x] Fixed #22224 -- Added note about supplying missing values for non-
nullable fields with blank=True.
Backport of cd6bddd44e0a1c3c6a96a3677f8366ef0e4b6782 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22224#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1331642ac9cbc4b23d06babc80142bc5%40djangoproject.com.
