Re: One set of stored procedure for multiple users

this is just one of the problems we as application developers encounter when we try to use database users as application users.

It's really very unwieldy. Here's our solution:

Basically, have the user log on thru a dialog box that you code that has nothing to do with the database user.

Then, behind the scenes, have the application log onto the database with the same user, no matter who is logged on.

Handle all the security yourself.

Now, as to your set of stored procedures:

alter a column onto each of your tables - USERNAME VARCHAR2(20) or whatever. Make it part of the key.

Pass the username into the stored procedure from the application. have the stored procedure read/write the table based on the additional AND clause of username=passed_username.

what do ya think?

rick

On 2 Jan 1997 21:09:30 GMT, hgu_at_honshu.tbu.att.com (Hongtao Gu) wrote:

>On 02 Jan 1997 15:54:06 GMT dave_at_fifthd.ca (Dave Macpherson)
>wrote:
>
>>Assuming that all six users are stored within the same instance, why
>>not just install the stored procedures under one of the user accounts
>>and create public synonyms in the other 5 user accounts to point to
>>the single set?
 

>>Regards,
>>Dave Macpherson
>
>Thank you for the suggestion.
>
>All six users are stored in one DB. If we install the stored procedures
>under one user accounts (let's say user A) and let all other users call
>them through synonym, all six users work with the same set of data -- the
>data owned by user A.
>
>Any other suggestions?
>
>Hubert
>
Received on Thu Jan 02 1997 - 00:00:00 CST