What you're thinking of is package variables. Variables declared in the header of a package will persist until they are changed or the user logs out. e.g. create or replace package p is my_login_name varchar2(30); procedure setname; end; / create or replace package body p is procedure setname is begin my_login_name := user; end; end; / You can now reference p.my_login_name outside of the package. Just call the proc from the login trigger. Jared oracle-l-bounce@xxxxxxxxxxxxx wrote on 03/11/2004 10:16:21 AM: > We have a fairly big query that takes about 6 hours > to complete. To speed up things, we thought of the > following: Create a logon trigger, which stores in memory > each user's info during login time. > > Then when the user clicks a button that starts this query, > to have his/her info already in memory as opposed to > getting it from disk somewhere. > > So basically, I just wanted to verify that a login trigger > does indeed store things in memory and keeps it there > until logout. Is that correct, or should I expect surprises? > > thanks, > maa > > ---------------------------------------------------------------- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > ---------------------------------------------------------------- > To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx > put 'unsubscribe' in the subject line. > -- > Archives are at //www.freelists.org/archives/oracle-l/ > FAQ is at //www.freelists.org/help/fom-serve/cache/1.html > ----------------------------------------------------------------- ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------