On Thursday, July 3, 2014 3:03:25 PM UTC+2, Jon Dufresne wrote: > > > Also, even if we find a place to show > > the errors, the user is (usually) in no position to correct them (after > all, > > there is no field he could change to fix it). > > I don't follow. In my specific example the user is able to change the > "name" field. In my opinion, the form should fail to validate because > the _user_ entered "newname" twice, for two different names when they > should be unique. The user is in the position to 1) make these > conflict and 2) correct them. >
I don't follow; if the user is able to change the "name" field; it's included in the form and uniqueness is checked, I thought we are talking about fields __not__ included in a form. Cheers, florian -- You received this message because you are subscribed to the Google Groups "Django developers" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/53cd7280-38ba-40cb-aff1-0f9558673b39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
