I'm starting to agree with this point. Form validation seems to fit best on the form template.
Can someone post an working example with this approach? I'm that kind of people which learn more from examples... ;-) -- JP Ian Bicking wrote: > I think validation can be very UI-oriented, not just data/model > oriented. For instance, I use TEXT columns all the time, unless there's > a concrete reason not to, because it is least likely to cause problems > in the future. And generally people have a tendency to restrict types > and formats more than they have to. I guess it's because databases are > often content repositories, and when they are they should be treated as > such. > > But I digress. When validation is UI, putting validation into the > view/template starts making more sense. I think this is a good > justification of Subway's inclination to use htmlfill_schemabuilder. In > a practical sense, when I'm collaborating with people at work, it's > often the people who are involved with the view that are also most > interested in the validation, but if it is in Python code it's largely > inaccessible to them. > > > -- > Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
