Re: Track all records read from a table

On Wed, Mar 23, 2016 at 4:28 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

The only reason to use a read trigger is for compliance purposes.

Wouldn't a read trigger be necessary, irregardless of whether the event
were output to a journal or physical file? My understanding is that the
only way to trap a read event would be via trigger. No?

​Correct...what I'm saying is that _IF_ you need a read trigger for
compliance, then it's better to have the trigger write to a journal since
journals are protected by the OS; you can't update or delete an entry in a
journal.

It'd be relatively easy to ​

​prove to an auditor that​ your journal is complete.

If you stick your read log in a DB table, then to prove it's complete you
have to have it journaled so that you can prove that no records in it were
updated or deleted.

Charles