[ http://issues.apache.org/jira/browse/DERBY-1610?page=all ]
Tomohito Nakayama updated DERBY-1610:
-------------------------------------
Attachment: DERBY-1610.diff
parameterMapping.diff
I tried to guess type of java.sql.Type when value was null ,
from drdaType as the patch.
As the result, the NetClientTest of jdbcapi/parameterMapping.java was failed
and got amount of difference.
I think this difference is too large to accept.
Originally, DERBY-1610 was issue around setBinaryStream(null).
Remembering the original problem,
it was more problematic point of this issue that setBinaryStream(null) to
character colum was failed though setBinaryStream(notNull) to character column
was successed, than difference between Engine and NetworkServer/NetworkEngine.
> 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: DERBY-1610.diff, parameterMapping.diff, 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
