Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <32981481.1156570106224.JavaMail.jira@brutus>
Date: Fri, 25 Aug 2006 22:28:26 -0700 (PDT)
From: "Tomohito Nakayama (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (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)
In-Reply-To: <19866578.1154244193912.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1610?page=all ]

Tomohito Nakayama updated DERBY-1610:
-------------------------------------

    Attachment: parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient

I tried to read difference of parameterMapping between Embedded and NetworkServer/NetworkClient, which is uploaded as parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient.

Nexts are the result which I could understand.

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.
This problem seems to exists in both setNull and passing null via setXXXX. 

2) Difference whether set method of BinaryStream/Blob/Clob is accepted to CHAR/VARCHAR/LONG VARCHAR or not.
set method of BinaryStream/Blob/Clob is accepted to CHAR/VARCHAR/LONG VARCHAR typed variable in NetworkServer/NetworkClient 
while it is not accepted in Embedded.

3) Difference whether setCharacterStream/setCLob for numeric type is accepted or not.
Embedded refuse and NetworkServer/NetworkClient accept.
it may be true only when the value can be interpreted as numeric.
Furthermore this may be true in DATE/TIME/DATETIME also if format of value is possible to interpret those types.

4) Execution of test for storedProcedure
storedProcedure is not tested in NetworkServer/NetworkClient case.

5) Execution of test for setObject(Blob/Clob)
setObject(Blob/Clob) is note tested in NetworkServer/NetworkClient case.

------------------------------------------------
What I couln't understand.
I found questionable message of "SPECIFIC CHECK OK" was in some test items of NetworkServer/NetworkClient case.
I could not understand what this message stands for .... 
Reading the code, it seems that those test items is skipped with this message in some condition, but not sure.

> 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