[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12424892 ] Tomohito Nakayama commented on DERBY-1610: ------------------------------------------
I surveyed execution of Network Server with jdb when TestNullChar.java was executed. In both of updateStreamAsNull and setNull, type information at server side was as next. DRDAConnThread_3[1] dump pmeta.types[0].typeId.baseTypeId pmeta.types[0].typeId.baseTypeId = { SQLTypeName: "CHAR" JDBCTypeId: 1 formatId: 17 wrapperTypeFormatId: 5 } It is very questionable that type is regarded as char when InputStream was passed. > 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