> Do you see a way to protect at the row or field level?

Certainly.
1.) you have a trigger function which calculates the hash at insertion of
the record. All gnumed tables for example inherit a table "gnumed_object"
which contains a "crc" attribute.
2.) you selectively dump the rows you are interested in, re-calculate the
hashes, and compare. That will tell you what has been modified. Nice way to
debug your triggers btw, if you fire the trigger on insert or update -
whatever manages to bypass your triggers / security functions will be caught
by comparing the hashes.

Horst



Reply via email to