#15326: ModelForm doesn't do unique checks if any of the fields is exluded
--------------------------------------+-------------------------------------
               Reporter:  liorsion    |         Owner:  nobody
                 Status:  closed      |     Milestone:  1.3   
              Component:  Forms       |       Version:  SVN   
             Resolution:  duplicate   |      Keywords:        
           Triage Stage:  Unreviewed  |     Has patch:  1     
    Needs documentation:  0           |   Needs tests:  0     
Patch needs improvement:  0           |  
--------------------------------------+-------------------------------------
Changes (by russellm):

  * status:  reopened => closed
  * resolution:  => duplicate


Comment:

 As far as I can make out, this is the same problem -- you may not be
 seeing an IntegrityError, but that's just a missing symptom, not an
 indication that it's a different problem.

 This report seems to be the underlying root cause of the problem described
 by #13091 -- i.e., the fact that uniqueness validation isn't performed
 when you have a form with a subset of the unique_together fields.
 list_editable is just a different way of creating such a form, and #13091
 is seeing integrity errors because the uniqueness condition is causing a
 database level failure, rather than just a failure to enforce a specific
 uniqueness condition.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/15326#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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to