[
https://issues.apache.org/jira/browse/DERBY-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533116
]
Dag H. Wanvik commented on DERBY-2065:
--------------------------------------
See repro attached to DERBY-3114.
Also reproducing my comments attached to that JIRA (a duplicate of this):
The standard says about disconnect statement, section 17.3, general
rule 6: If any SQL-connection in L is active, then an exception
condition is raised: invalid transaction state - active SQL-transaction.
According to section 23.1 SQLSTATE (p.1075):
Subcondition: Active SQL transaction
subclass: 001
so, in this case, so it would appear that the use of 25001 is correct,
not 25000. I suggest we change embedded to use 25001 also, and release
note it, since it has application impact.
> Network and embedded difference in SQLSTATE and message when
> Connection.close() with open transaction.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2065
> URL: https://issues.apache.org/jira/browse/DERBY-2065
> Project: Derby
> Issue Type: Bug
> Components: Network Client, Network Server
> Reporter: Bernt M. Johnsen
> Priority: Minor
>
> Network and embedded difference in SQLSTATE and message when
> Connection.close() with open transaction.
> ----------- NetworkClient --------------
> Message: Cannot close a connection while a transaction is still active.
> SQLState: 25001
> ----------- Embedded --------------
> Message: Invalid transaction state.
> SQLState: 25000
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
