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] Closed: (DERBY-1519) 'setAsciiStream' uses different encodings for embedded and client
Date Mon, 08 Oct 2007 11:20:50 GMT

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

Kristian Waagan closed DERBY-1519.
----------------------------------


Since there has been no response on merging the fix with 10.2 and we have pushed 10.3 out
the door, I'm closing this issue without merging it with the 10.2 branch.

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


Mime
View raw message