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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2011/01/13 18:31:49 UTC
[jira] Closed: (DERBY-1938) Add support for setObject(, null)
[ https://issues.apache.org/jira/browse/DERBY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik closed DERBY-1938.
--------------------------------
> 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
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.7.1.1
>
> Attachments: derby-1938-1a-reworked_patch.diff, derby-1938-1b-reworked_patch.diff, 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.