Very Computer

I am working with a web app that allows users to update/insert values. I
would like to track changes via triggers, but I can't figure out how to
determine the user who is making the change. All of the interaction between
the web server & db server occurs under one account - is it possible for me
to determine the user who is making the change based on their login. Any
ideas?

Does your web app use Session variables or something to
track the user name?  You could create a field in your
table to store the user.  Then change the code so that
every web app update also changes the <user> field in that
table to the current Session user.  Then the trigger can
grab that field from the inserted table in the trigger.

Quote:>-----Original Message-----
>I am working with a web app that allows users to

update/insert values. I

Quote:>would like to track changes via triggers, but I can't
figure out how to
>determine the user who is making the change. All of the
interaction between
>the web server & db server occurs under one account - is
it possible for me
>to determine the user who is making the change based on
their login. Any
>ideas?

>.

I thought about doing something similar to that, but figured my way was
wrong... Thanks for pointing me in the right direction.

Quote:> Does your web app use Session variables or something to
> track the user name?  You could create a field in your
> table to store the user.  Then change the code so that
> every web app update also changes the <user> field in that
> table to the current Session user.  Then the trigger can
> grab that field from the inserted table in the trigger.

> >-----Original Message-----
> >I am working with a web app that allows users to
> update/insert values. I
> >would like to track changes via triggers, but I can't
> figure out how to
> >determine the user who is making the change. All of the
> interaction between
> >the web server & db server occurs under one account - is
> it possible for me
> >to determine the user who is making the change based on
> their login. Any
> >ideas?

> >.