The trigger writes a easily readable file, the jounal is more for
auditing by skilled users.
Monnier, Gary wrote:
Why use a trigger when you can journal the table? The journal has jobinfo, creation date, job identifier, program making the change and even
remote IP address in addition to having the entire row's contents.
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
Sent: Wednesday, October 30, 2013 12:44 PMsalesrep (who has _some_ control over pricing) says he didn't do it, and no
To: Midrange Systems Technical Discussion
Subject: Log file of file changes
We had an issue recently about how a couple of prices got changed. The
one in the office remembers doing it. In fact, it was the sales rep who
brought it up wanting to know what the %#@* is going on? :) By looking at
month end backups, I know it happened sometime in August. Nothing like
bringing it to our attention on a timely basis, right?
I think it's a great idea and it seems to me to be an ideal use for a
Anyway, in discussing it, the buying VP suggested a log file of changes.
trigger. Whenever a record is added/updated/deleted, just have the trigger
write the record to this log file. It can have the same record layout as
the file in question, plus add a few fields such as user and timestamp.
Seem reasonable? I've never written a trigger before but I can figureit out.
The file is currently journaled, but that's not really what journaling is
company. Unless I say so.
Thanks for any ideas.
VP Information Systems
P.O. Box 13369
Ft. Wayne, IN 46868-3369
The opinions expressed are my own and not necessarily the opinion of my
--list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-lmoment to review the archives at http://archive.midrange.com/midrange-l.
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact