Adrian Holovaty wrote: >> but you *can* do that now, the only difference between what is now and >> what you are proposing is that you call validators, what are now >> Fields and you would call it >> CharField( validators=[USState, IsAllUpperCase] ) >> where you can now write >> ComboField( CharField, USStateField, IsAllUpperCaseField ) > > Exactly. Gary, I think maybe you're missing the subtleties of how > Fields work, which I can't fault you for, as I haven't written most of > the documentation for this stuff yet. :)
Aha! I told you I was missing something ;) A simple example clears all that up. I still think that calling them validators to apply to simple fields is more natural. It's closer to the database model of fields and check constraints and probably more immediately understandable by us mere mortals. I accept now that either way is just as easy though. Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
