[
https://issues.apache.org/jira/browse/DERBY-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897106#comment-13897106
]
Mamta A. Satoor commented on DERBY-4805:
----------------------------------------
Hi Knut, thanks for fixing the problem by putting the / in the jdbc url(and
taking an 'a' out from the dbname to make sure that we are still at 1024 limit
for positive test and at 1025 for negative test) to make it absolute path. I
made the changes on my Windows machine and the test ran fine. I will go ahead
and commit the changes. Thanks again.
> 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: backport_reject_10_10, derby_triage10_9
> Fix For: 10.11.0.0
>
> 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, d4805-test-ufs.diff
>
>
> 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)
