Re: Trigger programme without a trigger.

On 11/06/2008, at 6:38 PM, Peter.Colpaert@xxxxxxxxxxx wrote:

The logging is not for auditing or rollback purposes, but to offer the
users a "history view" of changes to items etc.

A journal provides a "history view" in addition to auditing changes and allowing rollback (if commitment control is active). Sure, you have to write (or buy) code that can read a journal entry and format it for display but that's no harder than writing a trigger or database program.

I don't see how journals could be used for that (plus that we deliberately
exclude some processes from logging, within the trigger programs, so as to
avoid logfile overload).

If the only reason for journaling is to log changes to certain files for "history" then don't journal the ones you aren't interested in "logging". If you are using journaling for its primary purpose then having additional records in the journal receiver isn't an issue. The so-called space concern evidenced by some is a furphy that can be properly managed by changing receivers regularly.

Still "bad use"?

Yes.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------