You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dyre Tjeldvoll (JIRA)" <de...@db.apache.org> on 2006/04/25 13:31:06 UTC
[jira] Updated: (DERBY-1236) Verify that applications can't
manipulate the transaction state while inside a distributed transaction.
[ http://issues.apache.org/jira/browse/DERBY-1236?page=all ]
Dyre Tjeldvoll updated DERBY-1236:
----------------------------------
Component: JDBC
Fix Version: 10.2.0.0
Version: 10.1.2.0
> Verify that applications can't manipulate the transaction state while inside a distributed transaction.
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1236
> URL: http://issues.apache.org/jira/browse/DERBY-1236
> Project: Derby
> Type: Improvement
> Components: JDBC
> Versions: 10.1.2.0
> Reporter: Rick Hillegas
> Assignee: Dyre Tjeldvoll
> Fix For: 10.2.0.0
>
> The next rev of the JDBC4 spec will clarify that applications may not call the following methods while inside distributed transactions: setAutoCommit( true ), commit(), rollback(), and setSavepoint(). We should verify that we conform.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira