That's great. Thanks.
On Feb 16, 2008 6:51 PM, <[EMAIL PROTECTED]> wrote:
> "sin(EaTing)," <[EMAIL PROTECTED]> writes:
>
> > Thanks, Dan.
> > The document I read seems already the latest, which is Derby Developer's
> > Guide Version 10.3.
> > And I am still confused about the isolation mode, I tr
"sin(EaTing)," <[EMAIL PROTECTED]> writes:
> Thanks, Dan.
> The document I read seems already the latest, which is Derby Developer's
> Guide Version 10.3.
> And I am still confused about the isolation mode, I traced the stored
> procedure using getTransactionIsolation() and the return value shows
Thanks, Dan.
The document I read seems already the latest, which is Derby Developer's
Guide Version 10.3.
And I am still confused about the isolation mode, I traced the stored
procedure using getTransactionIsolation() and the return value shows the
isolation level was changed, I am not sure about t
sin(EaTing), wrote:
*In order to preserve transactional atomicity, database-side JDBC
procedures that use
nested connections have the following limitations.
• Cannot issue a commit or rollback, unless called within a CALL statement.
• Cannot change connection attributes such as auto-commit.
*
Hi,
I am writing some stored procedure for Derby. And I am confused about the
transaction settings for a Derby stored procedure using a nested connection.
Actually I am trying to modify the transaction isolation level to something
like Serializable or Read Committed, and also change the auto commit
