Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Fri, 14 Jul 2006 16:31:23 -0400
From: "Lance J. Andersen" <Lance.Andersen@Sun.COM>
Subject: Re: [jira] Commented: (DERBY-1501) PreparedStatement#setNull(int
 parameterIndex, int sqlType) throws SQL Exception if given sqlType is
 LONGVARBINARY in embedded mode
In-reply-to: <18921303.1152712112909.JavaMail.jira@brutus>
Sender: Lance.Andersen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <44B7FF1B.5060309@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_4RWzfq0ed7xw5qBo/TZIQg)"
References: <18921303.1152712112909.JavaMail.jira@brutus>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)

This is a multi-part message in MIME format.

--Boundary_(ID_4RWzfq0ed7xw5qBo/TZIQg)
Content-type: text/plain; format=flowed; charset=UTF-8
Content-transfer-encoding: 7BIT

i have removed the rogue sentence in its entirety from the javadocs for 
setNull(int,int, String) as it is not needed and is not correct in 
regards to typeCode.

-lance

Daniel John Debrunner (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420620 ] 
>
> Daniel John Debrunner commented on DERBY-1501:
> ----------------------------------------------
>
> Knut Anders indicates
>
> setNull(int,int,String)
>  - If a JDBC driver does not need the type code or type name
>   information, it may ignore it. 
> setNull(int,int)
>     You must specify the parameter's SQL type.
>
> Interesting, here the issue is about setNull(int,int) which doesn't have that comment about ignoring typeCode.
> Could the omission be intentional and the wording in setNull(int,int,String) meant to be clearer, so that
> one of typeCode or typeName could be ignored, but not both?
>
> With setNull(1, Types.LONGVARBINARY) it is saying send a NULL of LONGVARBINARY to the engine,
> the engine should then treat it the same as a cast of a LONGVARCHAR FOR BIT DATA to the target type.
>
>
>
>
>   
>> PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode
>> ----------------------------------------------------------------------------------------------------------------------------------
>>
>>          Key: DERBY-1501
>>          URL: http://issues.apache.org/jira/browse/DERBY-1501
>>      Project: Derby
>>         Type: Bug
>>     
>
>   
>>     Versions: 10.1.1.0
>>  Environment: WindowsXP
>>     Reporter: Markus Fuchs
>>  Attachments: ByteArrayTest.java
>>
>> When inserting a row into following table
>> BYTEARRAY_TEST( ID int, BYTEARRAY_VAL blob)
>> PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY. You must give sqlType BLOB to make the insert work. The same test works using sqlType LONGVARBINARY in network mode. The following combinations don't work:
>> Column type               sqlType not working             mandatory sqlType
>> BLOB                           LONGVARBINARY                 BLOB
>> CLOB                           LONGVARCHAR                    CLOB
>> The issue here is that first Derby behaves differently in network and embedded mode. And secondly, should accept LONGVARBINARY/LONGVARCHAR for BLOB/CLOB columns.
>>     
>
>   

--Boundary_(ID_4RWzfq0ed7xw5qBo/TZIQg)
Content-type: text/html; charset=UTF-8
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
i have removed the rogue sentence in its entirety from the javadocs for
setNull(int,int, String) as it is not needed and is not correct in
regards to typeCode.<br>
<br>
-lance<br>
<br>
Daniel John Debrunner (JIRA) wrote:
<blockquote cite="mid18921303.1152712112909.JavaMail.jira@brutus"
 type="cite">
  <pre wrap="">    [ <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420620">http://issues.apache.org/jira/browse/DERBY-1501?page=comments#action_12420620</a> ] 

Daniel John Debrunner commented on DERBY-1501:
----------------------------------------------

Knut Anders indicates

setNull(int,int,String)
 - If a JDBC driver does not need the type code or type name
  information, it may ignore it. 
setNull(int,int)
    You must specify the parameter's SQL type.

Interesting, here the issue is about setNull(int,int) which doesn't have that comment about ignoring typeCode.
Could the omission be intentional and the wording in setNull(int,int,String) meant to be clearer, so that
one of typeCode or typeName could be ignored, but not both?

With setNull(1, Types.LONGVARBINARY) it is saying send a NULL of LONGVARBINARY to the engine,
the engine should then treat it the same as a cast of a LONGVARCHAR FOR BIT DATA to the target type.


  </pre>
  <blockquote type="cite">
    <pre wrap="">PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode
----------------------------------------------------------------------------------------------------------------------------------

         Key: DERBY-1501
         URL: <a class="moz-txt-link-freetext" href="http://issues.apache.org/jira/browse/DERBY-1501">http://issues.apache.org/jira/browse/DERBY-1501</a>
     Project: Derby
        Type: Bug
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
  <blockquote type="cite">
    <pre wrap="">    Versions: 10.1.1.0
 Environment: WindowsXP
    Reporter: Markus Fuchs
 Attachments: ByteArrayTest.java

When inserting a row into following table
BYTEARRAY_TEST( ID int, BYTEARRAY_VAL blob)
PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY. You must give sqlType BLOB to make the insert work. The same test works using sqlType LONGVARBINARY in network mode. The following combinations don't work:
Column type               sqlType not working             mandatory sqlType
BLOB                           LONGVARBINARY                 BLOB
CLOB                           LONGVARCHAR                    CLOB
The issue here is that first Derby behaves differently in network and embedded mode. And secondly, should accept LONGVARBINARY/LONGVARCHAR for BLOB/CLOB columns.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--Boundary_(ID_4RWzfq0ed7xw5qBo/TZIQg)--