[
https://issues.apache.org/jira/browse/DERBY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-1938:
-----------------------------------
Derby Info: (was: [Patch Available])
Clearing patch available flag. No activity on this for a long time.
If anyone feels the itch, please help drive this issue to completion.
It is not quite clear to me what is actually holding it back, but there seems
to be uncertainty on how it resolve the issue.
> 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
> Assigned To: Tomohito Nakayama
> 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.
