On 7/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > I haven't given this a ton of thought, but my own opinion is that > validator_list should go away, in favor of custom Field subclasses > that know how to validate themselves, and/or validate_FOO() method > hooks on the model. Basically, it would work a lot like newforms > custom fields and forms.
I guess my concern is that I'm not sure what db Field.to_python is for. Model.validate() can raise ValidationErrors, but you can easily get cleaned_data from a Form that still fails Model.validate(). I'm not sure how the Model.validate() exceptions are round-tripped back to the Form. It just seems too easy to forget to call Model.validate and end up with bad model data -- or to call it but have extra code in order to round trip another form. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
