[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429286 ] Tomohito Nakayama commented on DERBY-1610: ------------------------------------------
Technically, I think we can make the calcJdbcTypeForNullValue() *more complete*. However, I'm not sure we should do it right now. At first, DERBY-1610 started from side effects of DERBY-1535, improvement of streaming from client to server. It was found this side effect of DERBY-1535 has meaning of partial fix for DERBY-310. Then, DERBY-1610 started. //Modification of DERBY-1535 will be overwrtten almostly by DERBY-1559. //However DERBY-1559 has the same side effect as DERBY-1535, because the code of DERBY-1559 passes InputStream object instead of byte array to the Engine as the code of DERBY-1535 does. Historically this issue had meaning of accepting side effect of DERBY-1535 (and DERBY-1559) as partial fix for DERBY-310, at least in my true mind. However, if it comes to *complete* fix for DERBY-310 around type compatibility, I concern that throwing many new exceptions may cause large impact to the user, even if it was the behavior in Embedded mode. If we aim *complete* fix for DERBY-310 around type compatibility, I think some more carefulness is needed, because sphere to be influenced is pretty large if we aim *completion* ... ....Well. I think we need to know what is the carefulness needed in this issue .... ....Release note .....? may be ....... > 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, 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
