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 Thu, 31 May 2007 17:00:16 GMT

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

Kristian Waagan updated DERBY-1519:
-----------------------------------

    Attachment: derby-1519-1a.stat
                derby-1519-1a.diff

'derby-1519-1a.diff' changes all uses of US-ASCII on the client to ISO-8859-1.
suites.All run without errors with Java 1.5, and I started a derbyall now.

Please raise your concerns if you have any, I will commit if the second test run goes well.

> '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
>            Reporter: 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.


Mime
View raw message