|
The journal is great, but hard to read for regular users. A timestamp
field with "update as row change" helps to follow changes in the same
record. The journal can not be modified.
I often use a trigger and a journal. The file created by the trigger can
be read by a program easy to use.
Also, you can use a trigger and a program that moves it to a file to
read it and show in an easy program.
____________________________________________________________________
On 01/06/2016 03:21 PM, Justin Taylor wrote:
I need to keep a permanent log of all data changes in a particular PF. I can think of two ways to accomplish this.
1. A DB2 journal with the receivers set to never expire.
2. A trigger that would write the before images to a separate PF.
I expect questions of "who changed what when" to be a weekly occurrence.
Either of those options sound better than the other? Anyone have a door #3?
-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
