#12223: Model field documentation needs clarification about validation
---------------------------------------------------+------------------------
Reporter: JohnDoe | Owner: nobody
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: 1.1
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by bitspace):
* status: closed => reopened
* resolution: invalid =>
* summary: EmailField does not actually validate => Model field
documentation needs clarification about
validation
Comment:
The documentation needs clarification as I also expected the model field
to perform validation. Google revealed this ticket for me.
There really needs to be a "gotcha" prominently in the documentation that
says what you said: "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:4>
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.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
