Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <8557246.1191843471005.JavaMail.jira@brutus>
Date: Mon, 8 Oct 2007 04:37:51 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3114) Harmonize sql state thrown when
 closing a connection with pending transaction between net end embedded
 drivers
In-Reply-To: <13853666.1191843352247.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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