RE: Locking records in DB2

> From: Paul Holm
> 
> How do you handle all these data and rule validations?

This has nothing to do with data concurrence, so whether they are
handled at the same time or not is an architectural decision.
Personally, I don't find generic validation to be robust enough in
general; there are often rules that require multi-file interactions and
so fall outside of the scope of field-level validation.  But it depends
on what kind of applications you write.  For simple data entry,
field-level validation is typically adequate.


> Cycles can be important but processor speeds are ever increasing and
> currently fast enough to make this a non issue.  We have this strategy
> proven in dozens of applications.

This is a short-sighted view, in my opinion, and is the sort of thing
that makes you need 16GB of memory on an iSeries, or a 3GHz processor to
edit RPG code.  I'm still of the mind that performance needs to be
designed in from the beginning, and a simple concurrence counter is
vastly more efficient than what you're suggesting.

Now, that doesn't mean that you can't use a generic field-level
validation approach; if that works for you, fine.  But as I pointed out
in my previous email, your design is already inadequate in the case of
multiple independent field groups.  That's part of the problem with a
generic approach... it sometimes does everything well except what is
needed.

Joe