Re: When is a stored procedure needed?
From: William Robertson <williamr2019_at_googlemail.com>
Date: Sun, 3 May 2009 00:22:32 -0700 (PDT)
Message-ID: <0a78b94d-d481-472c-bee3-b54b4781d097_at_s20g2000vbp.googlegroups.com>
On May 2, 6:39 am, Phper <hi.steven..._at_gmail.com> wrote:
> Is it suggestible to write a stored procedure for registering or sign-
> in?
Date: Sun, 3 May 2009 00:22:32 -0700 (PDT)
Message-ID: <0a78b94d-d481-472c-bee3-b54b4781d097_at_s20g2000vbp.googlegroups.com>
On May 2, 6:39 am, Phper <hi.steven..._at_gmail.com> wrote:
> Is it suggestible to write a stored procedure for registering or sign-
> in?
Obviously a database connection will need to be established in order for any procedure stored in the database to be accessible to the user, so you would have to connect first to some generic account in order to call it. Then there is the problem that PL/SQL can't reconnect you as another user, although it could issue an ALTER SESSION to change the default schema, or enable some roles, or change some global variables you might use to identify application users. It all depends on what you are trying to do, how you define user accounts, how you want the login/register process to work, what the front end application is written in etc, hence the replies above. Received on Sun May 03 2009 - 02:22:32 CDT