Re: Login Triggers

From: Maryann Atkinson <maryann_30_at_yahoo.com>
Date: Fri, 12 Mar 2004 14:07:25 -0500
Message-Id: <5.2.1.1.2.20040312140345.01aac108@pop.netaddress.com>

At 01:43 PM 3/12/2004, you wrote:
> > I'm confused. The original question was asked by the person named Maryann,
> > so I'm not sure about the "we" part.

Its ok, I've been confused for 30 some years...

I meant "we" as in us here in my department...

> If your intention is to pre-run query and store results in memory, > then yes, that would be the best solution, in my opinion.

yes, thats why I too thought login triggers might have an advantage...

> > Login trigger is a procedure and not a mechanism for storing things. If
> you
> > want to check something and deny login based on some additional
> criteria or
> > turn on things like event 10046 for some classes of users, then yes, login
> > trigger would have an advantage.

Yes, but we could upon login issue a query, and store the results into some global memory variables, right?

> Now you gave me an idea. Being a BDBAFH, I'll implement it sooner or later.

Huh?

thanks again
maa

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Fri Mar 12 2004 - 13:05:53 CST