commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Updated: (DBCP-168) [dbcp] add/enhance toString() Method to DelegatingCallableStatement for sql debugging
Date Mon, 10 Jul 2006 05:20:32 GMT
     [ ]

Phil Steitz updated DBCP-168:

    Bugzilla Id:   (was: 33983)
    Fix Version: 1.3

> [dbcp] add/enhance toString() Method to DelegatingCallableStatement for sql debugging
> -------------------------------------------------------------------------------------
>          Key: DBCP-168
>          URL:
>      Project: Commons Dbcp
>         Type: Improvement

>  Environment: Operating System: All
> Platform: PC
>     Reporter: Ralf Hauser
>     Priority: Minor
>      Fix For: 1.3

> 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.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message