#12223: EmailField does not actually validate
---------------------------------------------------+------------------------
Reporter: JohnDoe | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.1
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by ubernostrum):
The implementation is not wrong, and the documentation is not wrong. Model
fields ''never'' perform any validation of this sort, and at the moment
are quite incapable of doing so. Forms can and do perform such validation,
and when a form is generated from a model which includes an `EmailField`,
the appropriate validation will be performed. Whenever and wherever a
model field has specialized constraints like this, the validation is
always handled by forms, and every such model field generates an
appropriate form field which performs that validation.
--
Ticket URL: <http://code.djangoproject.com/ticket/12223#comment:3>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=.
