Working on that. We have verified the following:
1) All rows are in temp. table 1 at after we create it.
2) All rows are in temp. table 1 at the point we start to
create temp. table 2. They remain there until we execute
the statement that prepares temp. table #2.
We tried caching statement handles so they're not reused. No
difference.
We fully turned off AutomCommit, RaiseError, and PrintError with
no effect.
It almost seems like DBD::Oracle is reusing/resetting something
at the Oracle level that's causing Oracle to act as if the first
table was committed. When you commit an Oracle global temporary
table, the rows are gone -- the idea is to only use the data
uncommitted in the session.
----
Steve Sapovits
GSI Commerce
[EMAIL PROTECTED]
> -----Original Message-----
> From: Dave K [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, October 04, 2002 1:15 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Oracle and global temporary tables
>
> Post some code...
>
> "Steve Sapovits" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> >
> > Has anyone used DBI to create and use Oracle's global temporary tables?
> > This mostly works for us, but we're having problems creating multiple
> > tables, where the ones after the first depend on the first via joins.
> >
> > ----
> > Steve Sapovits
> > GSI Commerce
> > [EMAIL PROTECTED]
> >
>
