db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1519) 'setAsciiStream' uses different encodings for embedded and client
Date Tue, 05 Jun 2007 07:49:26 GMT

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

Kristian Waagan updated DERBY-1519:

           Derby Info: [Release Note Needed]
    Affects Version/s:

Ticked the "Release Note Needed" flag, and added 10.3 to the affected list.

I don't think the release note can be called fine, if people don't understand what it means.
I'll have given it another try.

This time I deleted the old file, but what is the preferred way of publishing updates to the
release note?
Must the file be named something special for the utility to pick it up?

> '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:,,
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-1519-1a.diff, derby-1519-1a.stat
> 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.

View raw message