[
https://issues.apache.org/jira/browse/DERBY-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499052
]
Kristian Waagan commented on DERBY-1519:
----------------------------------------
Would people object to just changing the encoding in the client from US-ASCII
to ISO-8859-1?
This would make Derby more compliant with JDBC, but could it also break
existing applications?
I have checked that the change does not break any tests for Clob, but it
remains to see if the same is true for PreparedStatement.setAsciiStream (on the
client).
> '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
>
> 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.
