Re: Lookup/Code table as hot block

on login trigger

usually web aps have a single super user who logins into the database on behalf of the real users and has a shared connection pool. The first time that this user logs in, the login trigger reads the table. The application has to accept the data and store it, either as a file on the app server or as a variable array in the application. There are many mechanisms, the exact one that you use would be tailored to your needs.

I'm sure that other members have seen other ways that this was implemented. I'm just giving examples of what I've seen.

--
http://www.freelists.org/webpage/oracle-l