#9209: ModelChoiceField raises ValueError when passed a non integer string
-------------------------------+--------------------------------------------
          Reporter:  Rozza     |         Owner:  nobody
            Status:  new       |     Milestone:        
         Component:  Forms     |       Version:  1.0   
        Resolution:            |      Keywords:        
             Stage:  Accepted  |     Has_patch:  1     
        Needs_docs:  0         |   Needs_tests:  0     
Needs_better_patch:  0         |  
-------------------------------+--------------------------------------------
Comment (by hgee...@osso.nl):

 A bare except will mask programming errors with an invalid to_field on a
 ModelChoiceField.
 A different approach would be to use the model field to validate the value
 before passing it to the queryset.
 Note that I do not use field.validate on purpose since it performs
 database lookups by itself.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9209#comment:11>
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.

Reply via email to