[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12424366 ] Tomohito Nakayama commented on DERBY-1610: ------------------------------------------
Using jdb, I found that next code is executed at NetworkServer in both case of setBinaryStream method with null and setNull method. Step completed: "thread=DRDAConnThread_3", org.apache.derby.impl.drda.DRDAConnThread.parseSQLDTA_work(), line=4,047 bci=722 4,047 ps.setNull(i+1, pmeta.getParameterType(i+1)); I think current implementation of NetworkClient/NetworkServer handle them in same way both to call setBinaryStream method with null value and to call of setNull method. > Engine take it as type compatibility error to update column typed as CHAR to > value passed via setBinaryStream(null), though Network Client and Network > Server does not take it as error. > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > 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: TestNullChar.java > > > There exists difference between Engine and Network Client/Engine around type > compatibility judgement in character typed column when null value was passed > as InputStream. -- 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
