db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Holthuizen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1938) Add support for setObject(<arg>, null)
Date Tue, 07 Sep 2010 05:29:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906676#action_12906676
] 

Patrick Holthuizen commented on DERBY-1938:
-------------------------------------------

I think, although the issue is marked as minor, it makes Derby easier to use and therefor
may have a positive impact on the adoption of Derby with starters. And as said before it is
completely in line with the JDBC 3.0 and 4.0 specification as Dag pointed out.

> Add support for setObject(<arg>, null)
> --------------------------------------
>
>                 Key: DERBY-1938
>                 URL: https://issues.apache.org/jira/browse/DERBY-1938
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>            Reporter: Dag H. Wanvik
>            Priority: Minor
>         Attachments: DERBY-1938.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message