Re: Q&A on Data Integrity .....Help

I can't really answer these question for question with applicable links, but
here's how I do it. This is for a completely custom database for tracking
information about mineral deposits worldwide, so this probably won't be
effective for things like packaged apps.

I do not allow my users to have access to the data tables. All database and
application users only have (appropriate) access to views, which are almost
the same structure as the table, just decodes against the lookup tables have
already been implemented.I also have a lookup table for any field that
should be standardized

The views then have INSTEAD_OF triggers implemented, and the "business
logic", or the data integrity rules for the application and data, are
implemented with the triggers.

I have users that use a variety of programs to access the database, my
Application Express application, Access, ARC, MapInfo, etc., so keeping all
of the "business rules" in the triggers alleviates the need to place that
logic in each possible program that can connect (primarily via ODBC).

I couldn't think of any other way to accomplish data integrity for this
scenario, so if others have any better ideas, I'd be interested to see them.




--
-- Bill Ferguson

Other related posts: