db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1166) Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction
Date Mon, 16 Jun 2008 12:11:45 GMT

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

Kristian Waagan closed DERBY-1166.
----------------------------------


Issue has been fixed.
See DERBY-2065 for details.

> Incorrect SQLState used in EmbedConnection.java.close() when there is an active transaction
> -------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1166
>                 URL: https://issues.apache.org/jira/browse/DERBY-1166
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>            Reporter: David Van Couvering
>
> Currently in EmbedConnection.close(), if there is an active transaction a SQLException
is thrown with SQLState.LANG_INVALID_TRANSACTION_STATE, or "25000".  But looking at the SQL
2003 specification, the correct SQL State should be "25001" - "Active SQL-Transaction" (see
section 17.3 - disconnect statement, under General Rules: "If any SQL-connection in L is active,
then an exception condition is raised: invalid transaction state ?
> active SQL-transaction.")
> Although the stability classification for SQL States is currently under debate, for now
we must assume that, although incorrect, this SQL State cannot be changed until the next major
release.

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