How to avoid using DB Views when View needs User() info
hughes.matt_at_gmail.com
Date: 12/13/04
- Previous message: Robert Semmering: "Generating classes for tables of a data base"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 13 Dec 2004 11:25:39 -0800
I am working on a legacy application that was originally built with
only standalone applications in mind. Each application made a
connection to the DB and held on to it for the life of the application.
During this time many views were created to simplify data retrieval;
however, the views the user_name from the User() (oracle) function to
execute the views. Now, however, we have a web application as well
that uses this database. I would like to use connection pooling but
with the application dependent on these views, and the views dependent
on User() information, I don't see how I can.
I was thinking it would be possible to insert information into a
temporary table that only that connection could see every time I
started a new connection. The view would then always read from the
temporary table to find out the user info. It could only read the rows
available to that connection. Is this something that is possible with
Oracle, MS_SQL, or Informix? Any other ideas?
- Previous message: Robert Semmering: "Generating classes for tables of a data base"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
