[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436793 ] Knut Anders Hatlen commented on DERBY-1610: -------------------------------------------
I'm sorry, I didn't notice the "FOR BIT DATA" part. I agree with your first comment, that csPrepStmt should be changed. setNull(Date) should fail on a VARCHAR FOR BIT DATA (VARBINARY) parameter. What worried me, was that I thought the test ran under embedded and expected the call to succeed. But it is a derbynet test and doesn't run under embedded, so that should not be a problem. I also agree that setNull(Types.TIME) and setTime(null) should behave the same way. Table B-5 in the JDBC spec says that setObject(java.sql.Time) can be used on parameters of type CHAR, VARCHAR, LONGVARCHAR or TIME. I would expect setNull(Types.TIME) and setTime() to accept the same parameter types as setObject(Time). > Resolve difference of type compatibility between Embedded and > NetworkServer/NetworkDriver > ----------------------------------------------------------------------------------------- > > Key: DERBY-1610 > URL: http://issues.apache.org/jira/browse/DERBY-1610 > Project: Derby > Issue Type: Bug > Components: Network Server, Network Client > Reporter: Tomohito Nakayama > Assigned To: Tomohito Nakayama > Attachments: DERBY-1610.diff, DERBY-1610_2.diff, DERBY-1610_3.diff, > DERBY-1610_4.diff, DERBY-1610_5.diff, parameterMapping.diff, > parameterMapping.diff, > parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient, > parameterMapping_3.diff, TestNullChar.java, TestTypeCompatibility.java, > XCL12.diff > > > There exists difference of type compatibility between Embedded and > NetworkServer/NetworkClient. > This issue tries to resolve it. -- 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
