RE: Login Trigger

From: John Flack <JohnF_at_smdi.com>
Date: Fri, 12 Mar 2004 10:59:34 -0500
Message-ID: <91AFBA9B76078B4E8340A383EADEF1DB7EE564@syn2kex1.smdi.com>

What do you mean by having the login trigger "store things"? What things do you want to store, and how long are they needed? How does this help the long query? The usual reasons for login triggers are: 1. Control security - who may log in, when, with what privileges. 2. Retrieve some information about the user to store for the duration of the session. This is often application specific.

-----Original Message-----

From: Maryann Atkinson [mailto:maryann_30_at_yahoo.com] Sent: Friday, March 12, 2004 10:45 AM
To: oracle-l_at_freelists.org
Subject: Re: Login Trigger

Some coworker told me that login triggers actually store things on disk instead, and that every time this stored info is needed, a disk access will have to occur instead, and that doesnt sound too great of a concept...

Does anyone who used login triggers extensively have any knowledge and/or opinion to share?

thanks,
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 - 09:56:46 CST