commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DBCP-168) [dbcp] add/enhance toString() Method to DelegatingCallableStatement for sql debugging
Date Sun, 21 Jun 2009 17:30:07 GMT

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

Mark Thomas updated DBCP-168:
-----------------------------

    Fix Version/s:     (was: 1.3)
                   1.4

A good idea but without a patch, push it to 1.4

> [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
>             Fix For: 1.4
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message