Re: One set of stored procedure for multiple users

On 02 Jan 1997 22:46:28 GMT, rickfor_at_scsn.net wrote:

>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

Thank you for the suggestion.

It is a good solution for a new product. But for an existing product of ~100 tables and ~400 stored procedure, it is costly because this needs modification of all the tables and stored procedure and populate them to all the customer.

Any other suggestions?

Hubert Received on Fri Jan 03 1997 - 00:00:00 CST