[
https://issues.apache.org/jira/browse/DERBY-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916928#action_12916928
]
Tiago R. Espinha commented on DERBY-4827:
-----------------------------------------
Ah, and indeed, like you said, this only affects the client driver. We already
support other encodings in the embedded one.
> Modify the documentation for the 10.7 release regarding the UTF-8 CCSID
> manager
> -------------------------------------------------------------------------------
>
> Key: DERBY-4827
> URL: https://issues.apache.org/jira/browse/DERBY-4827
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.7.0.0
> Reporter: Tiago R. Espinha
>
> With the introduction of UTF-8 support in the client driver (DERBY-728), the
> documentation regarding the length of the arguments (RDBNAM, USRID, etc) will
> become misleading.
> On the list, Kathey has identified [1] one of such spots. Before releasing,
> we should try to find any other occurrences and fix them accordingly. Please
> note that the UTF-8 is a variable length encoding and as such, since we are
> maintaining the 255-byte length cap, the length in characters will now be
> variable.
> Regular ASCII characters still take 1 byte, Latin and other extended
> characters take 2 bytes, Chinese characters take 3 bytes and some special
> characters take 4 bytes. [2]
> [1] - http://old.nabble.com/Database-name-length-tt29691419.html
> [2] - http://www.utf8-chartable.de/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
