Re: When is a stored procedure needed?

From: Michael Austin <maustin_at_firstdbasource.com>
Date: Wed, 06 May 2009 08:11:54 -0500
Message-ID: <H_fMl.32677$ZP4.3110_at_nlpi067.nbdc.sbc.com>



joel garry wrote:
> On May 3, 12:22 am, William Robertson <williamr2..._at_googlemail.com>
> wrote:

>> 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.
> 
> I have come to believe this person is using this and other volunteer
> resources to collect information and then post it as his own for
> profit.  Check posting history.  Please feed the troll garbage.
> 
> jg
> --
> _at_home.com is bogus.
> http://www.google.com/search?hl=en&q=%22yellow+rambler%22+%22black+bmw%22&btnG=Google+Search&aq=f&oq=


anyone that pays these sites for information you can get for free on the myriads of reputable sites deserves what they get. Received on Wed May 06 2009 - 08:11:54 CDT

Original text of this message