You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tomohito Nakayama (JIRA)" <de...@db.apache.org> on 2006/10/07 16:00:20 UTC

[jira] Assigned: (DERBY-1938) Add support for setObject(, null)

     [ http://issues.apache.org/jira/browse/DERBY-1938?page=all ]

Tomohito Nakayama reassigned DERBY-1938:
----------------------------------------

    Assignee: Tomohito Nakayama

> Add support for setObject(<arg>, null)
> --------------------------------------
>
>                 Key: DERBY-1938
>                 URL: http://issues.apache.org/jira/browse/DERBY-1938
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Dag H. Wanvik
>         Assigned To: Tomohito Nakayama
>            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