>In fact we are using Oracle. The application need not be DBMS neutral.
>My problem is whether this locking can be done from the EJB side?
>Moreover the V$open_cursor table will give only the name of the
>database user, right?
>I want the name of the user who has logged on to our application.
This could get interesting - do you have a table that lists the users and
their names ? Otherwise I think it depends on how Oracle authenticates the
userids. I seem to recall you can have Oracle have its own internal
authentication or you can have the DBMS assume that the O/S has
authenticated. In which case you could load in stuff from the O/S data
store eg. passwd file in Unix ?
Actually I have a question here regarding the authentication here. Is the
database connection to the app server driven under a single userid eg. a
'master user' or via the actual userids of users ? I would assume that a
master user would be the case (want to add dbms userids for anyone who can
sign onto the web site ?). In this case the userid would not be reflected
because the master userid owns all the connections and threads. In this
case you will have to work out your own application mechanism to determine
who the user is.
Remember how I said that this could get messy ??:-)
cheers,
eddie
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
