db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4805) Increase the length of the RDBNAM field in the DRDA implementation
Date Tue, 04 Feb 2014 18:48:11 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mamta A. Satoor updated DERBY-4805:

    Attachment: DERBY4805_patch4_stat.txt

Attaching patch DERBY4805_patch4_diff.txt which is ready for commit. It 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. If there are no further comments, I will go ahead and commit the patch
on Thursday. 
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.
I will go ahead and log a jira for this behavior. Hopefully there won't be many user environments
where client and server are at different version levels and trying to give a really long db

> 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:
>            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

View raw message