>Subject: What's the best way to do this?
>From: Earl Hokens <hokens_at_ti.com>
>Date: 6/29/98 04:14 GMT
>Message-id: <3597BD4A.ADDE421D_at_ti.com>
>
>Running Oracle 8.
>
>I need to construct a temporary table from a Price
>table and a change table. (I know temp tables are
>not possible in Oracle) The "temp" table is
>constructed on user login and destroyed on user
>logout. The "temp" table has multiple queries and
>updates done to it (queries must show the all
>updates) on exiting the applet all changes to the
>"temp" table are recorded in the change table.
>
>What is the best way of accomplishing this?
>
>Possible answers I have (offer others if you know one!) are:
>
>1) put changes to the change file (commit them on
>exit) and queries are always the joins of price and
>change tables. Do uncommitted changes show on a
>query?
>
>2) create another table on startup and drop it on
>exit.
>
>3) ?????
>
>Regards,
>Earl
Hi Earl,
Have you considered using a view which is defined as the join between the
price and change tables ? This would not have to be dropped and recreated at
user logout/login.
The updates to the change table would be visible prior to commit, but only in
the session that issued the update, so if you, for example update the change
table in one form and then issue an open_form(form_name, new_session) (I think
that's the syntax, but don't hold me to it), then the uncommitted changes will
not be visible in the new form. However, the default option when issuing
open_form is to use the current session.
HTH
Rob
P.S. If this reply is as clear as mud then please mail me and I will attempt
to explain it more clearly.
Received on Mon Jun 29 1998 - 16:40:08 CDT
