That is exactly what my design would be given the
option. Thanks for concurring.
I have also been asked if the trigger can fire
off a pop-up box in the app to ask for a reason
for change that needs to be in the audit record
as well. Yeah, really... that's what they want.
Another option suggeste
g.ufl.edu>cc:
Sent by: root Subject: RE:
We call them Journal tables.
Great technique.
OraCop
--- "Lisa R. Clary" <[EMAIL PROTECTED]> wrote:
> Since we are in the medical records business, we too
> have the same
> guideline. What we do, is create an exact table
> replica (we call it an
> archive table and it does not have constraints) t
Steven - If you need this level of detail, have you considered LogMiner?
Just a thought.
Dennis Williams
DBA, 40%OCP
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Wednesday, November 13, 2002 10:49 AM
To: Multiple recipients of list ORACLE-L
This is for FDA regulation com
Since we are in the medical records business, we too have the same
guideline. What we do, is create an exact table replica (we call it an
archive table and it does not have constraints) to which before every insert
and update on the primary table, sends the row data to the archive table. It
stores
This is for FDA regulation compliance. The audit
records need to show every change made to the
source table in order of change.
WHile audit the table will show who changed the
record, it won't show what was changed.
Steve
--- Yechiel Adar <[EMAIL PROTECTED]> wrote:
> In my browsing of the oracl
Listers,
Oracle 8.1.7
I am looking for any whitepaper(s) that can
provide guidelines on the creation, use,
performance and limitations of triggers.
I need to create triggers on possibly 45 tables
for auditing purposes. The first draft
requirements document indicates denormalizing
data and gener
