commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33983] New: - [dbcp] add/enhance toString() Method to DelegatingCallableStatement for sql debugging
Date Sun, 13 Mar 2005 07:47:28 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33983>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33983

           Summary: [dbcp] add/enhance toString() Method to
                    DelegatingCallableStatement for sql debugging
           Product: Commons
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: hauser@acm.org


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.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message