> 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
- Re: tampering withelectronic health records Andrew po-jung Ho
- Re: tampering withelectronic health records Karsten . Hilbert
- Re: tampering withelectronic health records Horst Herb
- Re: tampering withelectronic health records Karsten . Hilbert
- Re: tampering withelectronic health records Andrew po-jung Ho
- Re: tampering withelectronic health records Andrew po-jung Ho
- Re: tampering withelectronic health records David Roseman, MD
- Re: tampering withelectronic health records Karsten . Hilbert
- Re: tampering withelectronic health records Horst Herb
- Re: tampering withelectronic health records Wayne Wilson
- Re: tampering withelectronic health records Horst Herb
- Re: tampering withelectronic health records Tim Cook
- Re: tampering withelectronic health records Horst Herb
- Re: tampering withelectronic health records Wayne Wilson
- Re: tampering withelectronic health records Wayne Wilson
- Re: tampering withelectronic health records Karsten . Hilbert
- RE: tampering withelectronic health records Jan . Cross
- Re: tampering withelectronic health records Dr Adrian Midgley
- Re: tampering withelectronic health records Andrew Ho
