I'm still wondering how one session can see data from another session.
The commit is irrelevent, as I should be able to have data persist for
the user session that is not affected by other sessions. This is the
case (independent results) when I'm using a sql session, but not when
I'm accessing through the app. Again, if anyone can shed some light on
this. Is it a connection pooling issue, where the session is shared,
or can it be caused by the xsql servlet? Any thoughts?
jbarney_ca_at_yahoo.ca (Barnoit) wrote in message news:<cd2c60c8.0403051741.7677854b_at_posting.google.com>...
> >
> > Just because it is a multipart query doesn't mean you have to "on commit
> > preserve rows". Do your multipart using the same session/connection and rows
> > from the first query will still be there.
>
> I'm using <xsql:dml> to insert into my gt table, and then <xsql:query>
> to query the temp table, and then I truncate the temp table. If I
> don't use preserve rows, the table is empty. You've got me thinking
> though, I'll check if there is an attribute in xsql to set the commit
> flag.
>
> thanks
>
> >
> > Change the table to on commit delete, and make sure your session gets
> > committed or rolled back after use.
> >
Received on Thu Mar 11 2004 - 10:23:26 CST
