Re: Passing a PL/SQL Table to another form

The idea to solve this problem with unique table names for each session is OK, but I don't like the side affect of this solution, and that is drop table statement that you have to execute on post form trigger. The same thing is with view. You may consider to use PL/SQL table(s) declared in database package specification. Reference to the PL/SQL table declared in database package is unique for each session. Plus, if one of your 2 columns has unique values in it, you can use 1 PL/SQL table only, storing unique value into index column, and the other value into regular table column.

DragonMaster wrote:

> You still might be able to use a database table. Since the table is
> temporary, you can create a different table for each user, on the fly using
> DBMS_SQL package and use the oracle session_id as part of the table name.
>
Received on Fri Dec 25 1998 - 00:00:00 CST