[DERBY-4827] Modify the documentation for the 10.7 release regarding the UTF-8 CCSID manager

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.7.1.1
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Tiago R. Espinha
• Created: 30/Sep/10 21:38
• Updated: 13/Jan/11 21:16
• Resolved: 26/Oct/10 13:06

Description

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/

Issue Links

• is blocked by: DERBY-728 Unable to create databases whose name containg Chinese characters through the client driver
• relates to: DERBY-4805 Increase the length of the RDBNAM field in the DRDA implementation