db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-1168) Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction
Date Fri, 21 Mar 2008 16:45:28 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden resolved DERBY-1168.
-----------------------------------

    Resolution: Duplicate

This is a duplicate of DERBY-2065 now fixed.


> Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction
> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1168
>                 URL: https://issues.apache.org/jira/browse/DERBY-1168
>             Project: Derby
>          Issue 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message