Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Mon, 27 Jun 2011 14:01:48 +0000 (UTC)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: 
 <769689464.43830.1309183308775.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <803292572.9351.1304009643239.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (OPENJPA-1990) Skip getting extend exception text
 when running on DB2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Curtis updated OPENJPA-1990:
---------------------------------

    Fix Version/s: 2.1.1

> Skip getting extend exception text when running on DB2
> ------------------------------------------------------
>
>                 Key: OPENJPA-1990
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1990
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>            Priority: Minor
>             Fix For: 2.1.1, 2.2.0
>
>
> When running on DB2 and we encounter an expected exception we spend a measurable amount of time calling back to the DB to get extended exception text[1]. With this JIRA I'm going to make this behavior configurable.
> [1] org.apache.openjpa.jdbc.sql.DB2Dictionary.appendExtendedExceptionMsg(...)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira