[
https://issues.apache.org/jira/browse/DERBY-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894009#comment-13894009
]
ASF subversion and git services commented on DERBY-4805:
--------------------------------------------------------
Commit 1565491 from [~mamtas] in branch 'code/trunk'
[ https://svn.apache.org/r1565491 ]
DERBY-4805(Increase the length of the RDBNAM field in the DRDA implementation)
This commit will allow RDBNAM to be 1024 bytes, thus lifting the limit from
current 255bytes. I have changed the existing boundary test case to test for
the new limit but the tests now use in-memory db jdbc url since on disk long
urls were running into problem because of OS/file system limitation on the
length of file name length.
As for newer client(version 10.11 and higher) going against an older
server(10.10 and lower which will not have the fix for DERBY-4805 and hence
will not accept the longer RDBNAM) with new RDBNAM limit, it will result in
protocol exception. This is because when the client makes the first connect
request to server, it has no way of knowing what server version it is talking
to and hence there is no way to catch the length violation on the client side
at this point.
> Increase the length of the RDBNAM field in the DRDA implementation
> ------------------------------------------------------------------
>
> Key: DERBY-4805
> URL: https://issues.apache.org/jira/browse/DERBY-4805
> Project: Derby
> Issue Type: Improvement
> Components: Network Client, Network Server
> Affects Versions: 10.7.1.1
> Reporter: Tiago R. Espinha
> Assignee: Mamta A. Satoor
> Labels: derby_triage10_9
> Attachments: DERBY4805_patch2_diff.txt, DERBY4805_patch2_stat.txt,
> DERBY4805_patch3_diff.txt, DERBY4805_patch3_stat.txt,
> DERBY4805_patch4_diff.txt, DERBY4805_patch4_stat.txt,
> DERBY_4805_diff_patch1.txt
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
