[ 
https://issues.apache.org/jira/browse/DERBY-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879093#comment-13879093
 ] 

Mike Matrigali commented on DERBY-4805:
---------------------------------------

note that testing may be complicated.  The length of a filename and length of a 
pathname is very system specific - and seems to be mostly file system dependent 
vs. OS.

http://en.wikipedia.org/wiki/Comparison_of_file_systems

I believe the original user having a problem was on NTFS/windows where it looks 
like the filename limit can be 255 "characters" - i am not sure what encoding 
the characters can be and thus how many bytes per character.  I don't remember 
if the problem was a specific long filename, or a combination of long unicode 
characters and long path.  The path 
length can be 32k unicode characters on ntfs and unlimited on the ext* file 
systems often used on unix, so that may
be an easier way to portably test the code.

> 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, 
> 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)

Reply via email to