Re: Passing Info to a trigger program

Several have suggested journaling. I know a journal is a log of changes
and we do use them in many ways now.

How would I tie the extra data not from the table to the journal entries?
It seems like I would have to go the route of adding a column to every
table and using a unique value in that column to tie it back to another
table with the extra information. We really want this to be as close to
real-time as possible and that seems a bit complicated with journals.

Brian

Original post:
I would like to be able to provide additional information that is

not available in the trigger buffer.

This additional information would be set by application programs

and used in the trigger program to create a log of changes for the
application.

I have considered a table, a data area, and an SQL global variable.
Are there other options? Which option would provide the

best performance?