Oracle users "self-righteous"? Snooty? Condescending? Hmmmm,
probably not any more than your average UNIX administrator/guru....
As for the trigger issue, I believe that Adam is correct, as
there really isn't any way that I know of to "pass" the value of
#appuser# to your games_audit table, since the trigger that is
performing the insert gets its data from the action that initiated
it, which in this case is an INSERT into the games table. In other
words, the trigger only "knows" about the OLD values of the
affected columns in games and the NEW values that are in the INSERT
or UPDATE statement agains games, not games_audit. Since you are
not using the value of #appuser# to update or insert into games,
the trigger has nothing to use on the insert into games_audit.
Since you do have any control over the trigger, and it fires
whenever you insert into games, one thing that you might consider
trying would be to put your insert statement for the games table
into a PL/SQL procedure, where you would pass the value of
#appuser# as one of the parameters. Then, after the insert query,
and before the commit, select from the games_audit table the rowid
of the row that was just inserted by the trigger and write an
update of games_audit that updates the value of change_user with
the value of #appuser# that you passed as an IN parameter. Then
commit and exit the procedure.
Phil