commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis Townsend (JIRA)" <>
Subject [jira] Commented: (DBUTILS-31) fillStatement setNull bug with the Derby JDBC driver
Date Thu, 06 Jul 2006 19:22:30 GMT
    [ ] 

Francis Townsend commented on DBUTILS-31:

This code was coded for the JDBC 3.0 specification.  It would need to be modified to run with
JDBC 2.1 drivers (check the JDBCMajor version to determine which code to use).  

Also, I have read that the Oracle JDBC driver throws an Exception.  Unfortunately, it does
not look as if there is no method that can determine this before calling the getParameterType
method.  Which means we would need to catch the exception and role back to the previous code,
namely use the VARCHAR type when setting null.  This would always be thrown by the Oracle
driver, severely slowing it down. 

So, I would suggest we hold off putting this into the next release until we have a better

> fillStatement setNull bug with the Derby JDBC driver
> ----------------------------------------------------
>          Key: DBUTILS-31
>          URL:
>      Project: Commons DbUtils
>         Type: Improvement

>     Versions: 1.0
>  Environment: Derby
>     Reporter: Francis Townsend
>      Fix For: 1.1

> This has been documented many times before, but I was not happy with the existing code
fixes.  The following small code snippet should fix it for all conforming JDBC drivers.
>     protected void fillStatement(PreparedStatement stmt, Object[] params)
>         throws SQLException {
>         if (params == null) {
>             return;
>         }
>         ParameterMetaData pmd = stmt.getParameterMetaData();
>         for (int i = 0; i < params.length; i++) {
>             if (params[i] != null) {
>                 stmt.setObject(i + 1, params[i]);
>             } else {
>                 stmt.setNull(i + 1, pmd.getParameterType(i + 1));
>             }
>         }
>     }
> The only difference is that you get the parameter meta data and pass that type information
to the setNull method.  This should neatly fix this problem, with a very slight additional

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