Am 26.02.2009 um 02:50 schrieb Chuck Hill:
Not sure for Anjo ... but one reason I can think of where
validation defined in the model is that this means that differing
applications using the same model (where the requirements may be
slightly different) are restricted to the same rules. Sometimes
good though.
That is a good point. Validations seem like something that properly
ought to be in the model. Maybe in cases like these, code
validations are the way to go? You could always alter the model at
load time, though that always seems like obscure hackery to me.
But then again, validation should keep you from - guess what - invalid
data out of your DB. So I kinda have a hard time imagining the same
model with different requirements. If it has, it's not the same model
anymore?
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
