Jonathan wrote: > > On Feb 4, 2006, at 7:03 PM, RJ Herrick wrote: > >> In validating my form input I look at my DB tables to see what types >> of input they will accept (valid values, maxlength, NULL ok, etc). >> This data is about the database, not the values coming in off the >> forms. It will stay the same until I alter my tables, which I won't >> be doing very often (in production at least :) ). So I'm looking to >> avoid gathering this metadata via DB calls every time I need to >> validate a form by instead using the cached metadata, stored >> somewhere by mod_perl. My thought was to put it into it's own >> namespace and have it available globally, loaded from one of my >> modules at startup. >> Does anyone else understand what I'm trying to say? I apologize if >> I'm not expressing myself in the right vernacular. >> Thanks, >> RJ Herrick > > > Oh. In that case... i put stuff like that in its own namespace during > the startup.pl phase. > > Suggestion though- (and this gets completely off topic) > > it might make sense to have some sort of form builder/validator class > > At the risk of making some people here cringe, in my projects I do > something like
Looks like you're trying to reinvent Data::FormValidator. -- Michael Peters Developer Plus Three, LP
