[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12425235 ] Tomohito Nakayama commented on DERBY-1610: ------------------------------------------
Reading the code, it seems that NetworkServer recognize the type of the parameter, according to the SQL and not according to the method which passes the parameter value. SQL to be executed in the TestNullChar.java is as next and type of the parameter is recognized as CHAR. INSERT INTO NULL_CHAR_TEST(CHAR_VALUE) VALUES(?) Ground of my reading is that type data is retrieved from Statement and not from FDODSC of SQLDTA. > 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
