You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/07/18 22:26:17 UTC
[jira] Updated: (DERBY-1519) 'setAsciiStream' uses different
encodings for embedded and client
[ http://issues.apache.org/jira/browse/DERBY-1519?page=all ]
Daniel John Debrunner updated DERBY-1519:
-----------------------------------------
Priority: Minor (was: Major)
Possible workaround is for the application to use getCharacterStream and apply encoding as required.
> 'setAsciiStream' uses different encodings for embedded and client
> -----------------------------------------------------------------
>
> Key: DERBY-1519
> URL: http://issues.apache.org/jira/browse/DERBY-1519
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.1.3.1, 10.2.0.0
> Reporter: Kristian Waagan
> Priority: Minor
>
> 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.
-
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