db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1938) Add support for setObject(<col>, null)
Date Thu, 05 Oct 2006 22:39:19 GMT
Add support for setObject(<col>, null) 

                 Key: DERBY-1938
                 URL: http://issues.apache.org/jira/browse/DERBY-1938
             Project: Derby
          Issue Type: Improvement
          Components: JDBC
            Reporter: Dag H. Wanvik
            Priority: Minor

Derby presently does not implement support for the method
PreparedStatement.setObject (and similarly for CallableStatement.setObject) 
when the supplied value is null, unless a type argument (3rd arg) is also present. 
That is, in:
    void setObject(int parameterIndex,
                              Object x)
                              throws SQLException
x can not be null. 

Derby will presently throw an SQLException (client: XJ021, embedded: 22005)
if x is null when calling this method on a preparedStatement.

Porting some applications may be made easier if this restriction is lifted.
See also discussion in DERBY-1904.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message