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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2007/10/08 13:37:51 UTC
[jira] Updated: (DERBY-3114) Harmonize sql state thrown when
closing a connection with pending transaction between net end embedded
drivers
[ https://issues.apache.org/jira/browse/DERBY-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3114:
---------------------------------
Component/s: JDBC
Summary: Harmonize sql state thrown when closing a connection with pending transaction between net end embedded drivers (was: Harminize sql state thrown when closing a connection with pending transaction between net end embedded drivers)
> Harmonize sql state thrown when closing a connection with pending transaction between net end embedded drivers
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3114
> URL: https://issues.apache.org/jira/browse/DERBY-3114
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.3.1.4
> Reporter: Dag H. Wanvik
> Priority: Minor
>
> * Embedded (thrown from EmbedConnection#close):
> State: 25000 (LANG_INVALID_TRANSACTION_STATE)
> Text in English locale: "Invalid transaction state."
> * Network client (thrown from Connection#checkForTransactionInProgress)
> State: 25001 (CANNOT_CLOSE_ACTIVE_CONNECTION)
> Text in English locale: "Cannot close a connection while a transaction is still active."
> I don't see why these should differ between the drivers. The network client
> error message is more explanatory, I think.
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.