Frank W. Zammetti wrote: > On Thu, June 8, 2006 1:09 pm, Michael Jouravlev wrote: > >> On the other hand, the whole idea of Struts/Commons Validator sucks >> big time, because database already has all necessary validations, >> domains, triggers, etc. Since most apps use database anyway, input >> data should either be validated directly by a database or by DAO; DAO >> should pull metadata from database to build validation/conversion >> rules. Seems that Ruby on Rails is closer to this approach, while most >> other frameworks do the same job twice or even three times. >> > > I *totally* disagree with this :) >
+1, and Frank didn't even mention that complex business-model-aware validations most likely _can't_ be done in the database without a pretty robust payer of triggers and stored procs, which are generally DB-specific: I don't want to validate zipcodes for addresses anwhere but at the outer-most levels of the app. I want form validation to be done as close to the form as possible. I want business-logic style validation to be done immediately following generic form processing. DB-level validation (references, etc.) handled last, and preferably the most generic. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
