Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 24 Feb 2015 03:23:31 +0000 (UTC)
From: "Phil Steitz (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12342113.1110732448000.118212.1424748211499@Atlassian.JIRA>
In-Reply-To: <JIRA.12342113.1110732448000@Atlassian.JIRA>
References: <JIRA.12342113.1110732448000@Atlassian.JIRA>
 <JIRA.12342113.1110732448000@arcas>
Subject: [jira] [Closed] (DBCP-168) [dbcp] add/enhance toString() Method to
 DelegatingCallableStatement for sql debugging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Phil Steitz closed DBCP-168.
----------------------------

> [dbcp] add/enhance toString() Method to DelegatingCallableStatement for sql debugging
> -------------------------------------------------------------------------------------
>
>                 Key: DBCP-168
>                 URL: https://issues.apache.org/jira/browse/DBCP-168
>             Project: Commons Dbcp
>          Issue Type: Improvement
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Ralf Hauser
>            Priority: Minor
>
> one of the beauties of mysql connector-J is that a stmt.toString() not just
> produces the object reference string but also the sql-statement that will be
> executed on the RDBMS server. (Thanks Mark Matthews!)
> Recently, I went through the excercise of porting a larger jdbc code-base from
> mysql to oracle. There may be many reasons to do this, but error handling in
> ojdbc14.jar is not one of it  :(   {the usual laziness of programmers when
> throwing an error: not saying which of the parameters caused it, not citing
> offending values, string positions of invalid characters, ... - it would cost
> them a few minutes to do better and save the developers using their jar days if
> not weeks!}
> Therefore the RFE:
> Not only directly pass on all values in DelegatingCallableStatement and
> DelegatingPreparedStatement to the delegate, but in the set*() methods gather
> enough information to be able to do something along the lines of
> com.mysql.jdbc.PreparedStatement.asSql()
> Sure one might say that this causes unneccessary overhead for production
> environments - o.k. perhaps there needs to be a configuration flag to set
> whether dbcp shall do this or operate as is.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)