[DERBY-4805] Increase the length of the RDBNAM field in the DRDA implementation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.11.1.1
• Component/s: Network Client, Network Server
• Labels: derby_backport_reject_10_10 derby_triage10_9
• Urgency: Normal
• Issue & fix info: High Value Fix, Newcomer, Patch Available
• Assignee: Mamta A. Satoor
• Reporter: Tiago R. Espinha
• Created: 19/Sep/10 13:28
• Updated: 09/Sep/16 09:53
• Resolved: 19/Feb/14 21:46

Description

Currently, whenever the client driver is used, there is a limit of 255 bytes for the database name. This is defined by the DRDA spec and there has been a discussion on the list [1]/[2] as to whether this limit should be raised due to the introduction of the new ACR that allows for UTF-8 characters.

UTF-8 characters can take up to four bytes and this reduces the limit in characters dramatically.

This should be an easy change as there is a codepoint that defines this limit.

[1] did not work but [2] did
[1] - http://old.nabble.com/Database-name-length-tt29691419.html
[2]http://apache-database.10148.n7.nabble.com/Database-name-length-td33182.html

Issue Links

• depends upon: DERBY-728 Unable to create databases whose name containg Chinese characters through the client driver
• is related to: DERBY-4827 Modify the documentation for the 10.7 release regarding the UTF-8 CCSID manager
• is related to: DERBY-6472 Behavior of RDBNAM longer than 255 bytes when server and clients are at different versions
• is related to: DERBY-6469 Change the documentation to reflect new RDBNAM limit of 1024 bytes