[
https://issues.apache.org/jira/browse/DERBY-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864584#comment-13864584
]
Mamta A. Satoor commented on DERBY-4805:
----------------------------------------
Thank you for reviewing the patch Kathey and Knut.
Going back to the allowable max length for RDBNAM, I looked through DRDA DDM
Architecture manual and see that there are lots and lots of DDM objects(listed
below) that use RDBNAM in their handshake between client and server(any DDM has
a maximum length limit of 32767) It seems like in order to decide the length,
we could go through each and everyone of those DDM codepoints in the manual and
try to find the maximum length possible for RDBNAM after taking into account
the lengths of the other data structures that make up that DDM. This can be
tedious and may not be necessary if we decide to come up with a reasonable
length of say 1024 or some such length for RDBNAM so that it is long enough to
not get bogged down by current 255 bytes limit(which can be limiting if we are
dealing with characters that take 4-bytes). Please let me know what your
thoughts are. Thanks
All of the following DDM objects use RDBNAM
ABNUOWRM, ACCRDB, ACCSEC, AGNPRMRM, BGNBND, BGNBNDRM,
BNDCPY, BNDDPLY, BNDSQLSTT, CHRSTRDR, CLSQRY, CMDATHRM,
CMDCHKRM, CMDNSPRM, CMDVLTRM, CMMRQSRM, CNTQRY,
DRPPKG, DSCINVRM, DSCRDBTBL, DSCSQLSTT, DTAMCHRM, ENDBND,
ENDDTARM, ENDQRYRM, ENDUOWRM, EXCSQLIMM, EXCSQLSET,
EXCSQLSTT, INTRDBRQS, MGRDEPRM, OBJNSPRM, OPNQFLRM,
OPNQRY, PKGBNARM, PKGBPARM, PKGNAM, PKGNAMCSN,
PKGNAMCT, PRCCNVCD, PRCCNVRM, PRMNSPRM, PRPSQLSTT,
QRYNOPRM, QRYPOPRM, RDBACCRM, RDBAFLRM, RDBATHRM,
RDBCMM, RDBNACRM, RDBNFNRM, RDBRLLBCK, RDBUPDRM,
REBIND, RSCLMTRM, SECCHK, SQLERRRM, SYNCLOG, SYNTAXRM,
TRGNSPRM, VALNSPRM
> 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: 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)
