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 "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2006/04/12 01:44:21 UTC

[jira] Updated: (DERBY-1168) Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction

     [ http://issues.apache.org/jira/browse/DERBY-1168?page=all ]

Mike Matrigali updated DERBY-1168:
----------------------------------

    Component: JDBC

> Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction
> -------------------------------------------------------------------------------------------
>
>          Key: DERBY-1168
>          URL: http://issues.apache.org/jira/browse/DERBY-1168
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Reporter: David Van Couvering
>     Priority: Minor

>
> 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