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 "David Van Couvering (JIRA)" <de...@db.apache.org> on 2006/03/30 00:22:29 UTC
[jira] Closed: (DERBY-1167) Incorrect SQLState used in
EmbedConnection.java.close() when there is an active transaction
[ http://issues.apache.org/jira/browse/DERBY-1167?page=all ]
David Van Couvering closed DERBY-1167:
--------------------------------------
Resolution: Duplicate
Duplicate to DERBY-1168, caused by JIRA hanging when I tried to post the bug report
> Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-1167
> URL: http://issues.apache.org/jira/browse/DERBY-1167
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
>
> EmbedConnection.close() should use SQLState 25001 - Invalid transaction state - active SQL-Transaction, when an attempt to close is made with an open transaction. From the specification of disconnect in SQL 2003: 'If any SQL-connection in L is active, then an exception condition is raised: invalid transaction state ? active SQL-transaction." Currently it is using 25000, which simply means "Invalid transaction state." Note the message is also very unhelpful, it simply says "Invalid transaction state."
> Although this is currently under debate, at this point we need to assume that SQL States can not change except across major release boundaries, so I am logging this bug but we can't fix it until 11.0.
--
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