Hello Knut.
By the way, I want to figure it out what is the actual range of
modification in DERBY-1610.
Knut Anders Hatlen commented on DERBY-1610:
Therefore, I think that it is better to fix all of them at once.
What is "all of them" here ?
Just setBlob and setBinaryStream ?
Or whole case of parameterMapping.java ?
Too high goal may block other task,
then reasonable goal should be established.
I think it is needed to analyze current difference of
parameterMapping.out between Embedded and Network Client in order to
consider the goal...
Best regards.
Tomohito Nakayama (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429427 ]
Tomohito Nakayama commented on DERBY-1610:
------------------------------------------
Oh...
Our comments were conflicted :)
I see.
Anyway it seems that I need to work on current implementation of NetworkClient.
I will try.
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.
--
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
