[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12430702 ] Tomohito Nakayama commented on DERBY-1610: ------------------------------------------
I correct description of 1)... 1) Difference around null. - Embedded regards null as different type as imcompatible in many combinations between types while -NetworkServer/NetworkClient regards null as different type in almost all combinations between types. +Embedded regards null value typed in different type as imcompatible in many combinations between types while +NetworkServer/NetworkClient regards them compatible in almost all combinations between types. This problem seems to exists in both setNull and passing null via setXXXX. > Updating column typed as CHAR to value passed via setBinaryStream(notNull) is > failed because of imcompatiblity of types though it was not taken as error > when setBinaryStream(null) > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > 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, > parameterMapping.diff, parameterMapping.diff, > parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient, > TestNullChar.java > > > There exists difference between updating character typed column to value > passed via setBinaryStream(notNullValue) and updating the column to value > passed via setBinaryStream(null). > This difference is problematic because it does not exist in Embedded mode. -- 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
