Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <26382515.1148677050723.JavaMail.jira@brutus>
Date: Fri, 26 May 2006 20:57:30 +0000 (GMT+00:00)
From: "Kathey Marsden (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-1354) Writer.write(int c) to writer from
 Clob.setCharacterStream(long pos) appends integer value, not character
In-Reply-To: <14624485.1148659529871.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-1354?page=all ]
     
Kathey Marsden resolved DERBY-1354:
-----------------------------------

    Fix Version: 10.1.2.5
     Resolution: Fixed
     Derby Info:   (was: [Patch Available])

Submitted to 10.1

Date: Fri May 26 13:53:59 2006
New Revision: 409746

URL: http://svn.apache.org/viewvc?rev=409746&view=rev


> Writer.write(int c) to writer from Clob.setCharacterStream(long pos) appends integer value, not character
> ---------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-1354
>          URL: http://issues.apache.org/jira/browse/DERBY-1354
>      Project: Derby
>         Type: Bug

>   Components: JDBC, Network Client
>     Reporter: Anders Morken
>     Assignee: Anders Morken
>     Priority: Minor
>      Fix For: 10.1.3.0, 10.1.2.5
>  Attachments: DERBY-1354.patch
>
> DERBY-1245-collateraldamage-v1.patch fixes a little bug in o.a.d.client.am.ClobWriter.java's write(int c) method.
> In it's original implementation the int parameter was passed directly to the StringBuffer.append() method, resulting 
> in the int being converted to it's string representation and then appended. (i.e. passing the char 'a' to write(int c) 
> would append the string "97" to the StringBuffer and thus the Clob. 97 is the ASCII code for the character 'a'.) 
> Please note that the patch is attached to DERBY-1245, as that was the Jira issue I was working on when I discovered
>  this. This issue is a placeholder of sorts. =)

-- 
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