#22224: Non-nullable blank string-based model field validation doesn't prevent
or
clean `None`
--------------------------------+---------------------------------------
Reporter: Simon Charette | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+---------------------------------------
Changes (by Jacob Walls):
* owner: nobody => Jacob Walls
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* status: new => assigned
* component: Database layer (models, ORM) => Documentation
Comment:
[https://groups.google.com/g/django-developers/c/GlYM25fdRnA Per mailing
list:]
> It does come up. It _is_ surprising that `blank` has this effect, and
I'm not convinced it says clearly anywhere how you should approach it…
Having weighed the possible behavior changes and found them wanting, we're
looking at documenting the `blank=True` and `null=False` idiom.
--
Ticket URL: <https://code.djangoproject.com/ticket/22224#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.ca713d03534e9b76f369ebb30ae81e4c%40djangoproject.com.
