db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1610) 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)
Date Mon, 21 Aug 2006 14:31:15 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429425 ] 
            
Tomohito Nakayama commented on DERBY-1610:
------------------------------------------

Regarding check on the client side, I found description of PRPSQLSTT in the spec of drda.
It seems that information for parameter seems to be handled in TYPDEFOVR/TYPDEFNAM.

It may be possible to check type at client side in drda. 

However not clear about currrent implementation of ClientDriver yet ...


> 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

        

Mime
View raw message