#13249: Feature request: ModelForm validation error handling after commit=False
-------------------------------------+-------------------------------------
Reporter: orokusaki | Owner: nobody
Type: Bug | Status: reopened
Milestone: | Component: Forms
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 0
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by legutierr):
* status: closed => reopened
* severity: => Normal
* resolution: wontfix =>
* easy: => 0
* type: => Bug
* stage: Unreviewed => Design decision needed
Comment:
I agree with orokusaki that although there is a better approach to that
described in the original ticket (i.e. the use of
`form.save(commit=False`)), there is, nonetheless, a problem in the way
that form.is_valid() and model validation validates `unique_together`.
Currently, model validation ignores all `unique_together` tuples where
*any* of the referenced fields are excluded; instead, model validation
should only ignore those `unique_together` tuples where *all* of the
referenced fields are excluded.
I am reopening this ticket with the purpose of marking it as a duplicate
of #13091.
--
Ticket URL: <http://code.djangoproject.com/ticket/13249#comment:5>
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-updates@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.
