[
https://issues.apache.org/jira/browse/DERBY-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4004:
----------------------------------
Attachment: derby-4004_10_4_diff.txt
Attached is a patch derby-4004_10_4_diff.txt which backports this change to
10.4. I am putting the change to 10.4 and 10.3 to avoid the change in error
message when attempting to connect with multibyte characters in the database
name after the fix for derby-4008 for new clients connecting to back rev
servers.
Running tests and will commit Monday if there are no objections.
> Remove required RDBNAM from ACCSEC. Use SECCHK RDBNAM if none is provided on
> ACCSEC
> ------------------------------------------------------------------------------------
>
> Key: DERBY-4004
> URL: https://issues.apache.org/jira/browse/DERBY-4004
> Project: Derby
> Issue Type: Sub-task
> Components: Network Client, Network Server
> Affects Versions: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.5.0.0
>
> Attachments: derby-4004-fix_new_protcoltest.diff,
> derby-4004_10_4_diff.txt, derby-4004_diff.txt
>
>
> Currently Derby requires RDBNAM on ACCSEC. The DDM spec lists it as optional.
> For DERBY-728, in order to negotiate the encoding, EXCSAT and ACCSEC will
> need to remain EBCDIC, so we want the RDBNAM to be optional. We can use the
> RDBNAM sent in SECCHK instead.
> Once this is done. Client can be changed to only send RDBNAM on ACCSEC if an
> EBCDIC conversion is possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
