[ http://issues.apache.org/jira/browse/DERBY-1166?page=all ]
Mike Matrigali updated DERBY-1166:
----------------------------------
Component: JDBC
> Incorrect SQLState used in EmbedConnection.java.close() when there is an
> active transaction
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-1166
> URL: http://issues.apache.org/jira/browse/DERBY-1166
> Project: Derby
> 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.
-
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
