Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <22104003.1181062829652.JavaMail.jira@brutus>
Date: Tue, 5 Jun 2007 10:00:29 -0700 (PDT)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1519) 'setAsciiStream' uses different
 encodings for embedded and client
In-Reply-To: <22370770.1153139174701.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501612 ] 

Myrna van Lunteren commented on DERBY-1519:
-------------------------------------------

The new release note is more explicit, I like it.

The release note file has to be named releaseNote.html.

The release note generator (see DERBY-2750) will figure out the latest
file of that name & pick that one, so you don't need to remove the old
one.

The release note generator will pick up the release notes whenever
it's marked release note needed or existing application impact, but
some people have ticked release note needed off when they attach a
release note, and leave existing application impact on.
So, probably best to tick 'application impact'.

Myrna


> 'setAsciiStream' uses different encodings for embedded and client
> -----------------------------------------------------------------
>
>                 Key: DERBY-1519
>                 URL: https://issues.apache.org/jira/browse/DERBY-1519
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client
>    Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: derby-1519-1a.diff, derby-1519-1a.stat, releaseNote.html
>
>
> The JDBC method 'setAsciiStream' uses different encodings for embedded and client. In the embedded driver, "ISO-8859-1" is used, in the client driver "US-ASCII" is used. The former is 8-bit, the latter is 7-bit. According to JDBC, the 8-bit encoding should be used for ASCII (see http://db.apache.org/derby/papers/JDBCImplementation.html#GetAsciiStream%28%29 ).
> The method 'getAsciiStream' should also be made to match in the two drivers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.