#25065: Should EmailField empty_strings_allowed be False
-------------------------------------+-------------------------------------
Reporter: CrazyCasta | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
`empty_strings_allowed` controls whether empty values may be stored as an
empty string or if they must be stored as null. In the case of
`EmailField`, empty strings are fine. See also the second paragraph in the
[https://docs.djangoproject.com/en/stable/ref/models/fields/#null
Field.null] docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/25065#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.56a0584d7228bc40a1f660e0768a8005%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
