RE: ALL I/O in single module was(ARGH!!! (was file open with LR))

> From: rob@xxxxxxxxx
> 
> I agree with validity checking in one place.  However I disagree about
an
> I/O module for it.  The validity checking could be in proper setup of
the
> database.

And I disagree that databases are designed to handle business rules.
You end up writing business logic in trigger programs, which is not what
they were intended to do.


> For instance with constraints and/or triggers then any updates
> done with any tool are checked.  And there is NO leak from someone who
> accessed the file without using the I/O module.

Personally, I've come to embrace the idea of using both.  Since triggers
and referential integrity really amount to writing business logic in
separate places, I prefer to combine all that logic in one I/O module
around each file (or group of related files), and then exclude all
access except through that module.

I only make files accessible as necessary, and for those files I do have
to leave open to the public, I can put a trigger on them.  If the
trigger senses an attempt to access the file OTHER than through the I/O
module, it denies the request.

Simple, clean, and all my business rules are in one piece of code.  This
is the best of both worlds.  This also allows the easy implementation of
things like row-level security and other features that DB2/400 doesn't
support natively.

Joe