[DBCP-168] [dbcp] add/enhance toString() Method to DelegatingCallableStatement for sql debugging

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix

Environment

Operating System: All
Platform: PC

• Bugzilla Id: 33983
• Assignee: Unassigned
• Reporter: Ralf Hauser
• Created: 13/Mar/05 16:47
• Updated: 24/Feb/15 03:23
• Resolved: 05/Mar/14 11:45

Description

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.