You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/03/18 22:49:50 UTC

[jira] Updated: (DERBY-4008) Only send RDBNAM on ACCSEC if EBCDIC conversion is possible

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

Myrna van Lunteren updated DERBY-4008:
--------------------------------------

    Attachment: releaseNote.html

10.5 rel mgr work - replacing <br> with <br/> so the releaseNotesGenerator can chew it.

> Only send RDBNAM on ACCSEC if EBCDIC conversion is possible
> -----------------------------------------------------------
>
>                 Key: DERBY-4008
>                 URL: https://issues.apache.org/jira/browse/DERBY-4008
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Network Client
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>             Fix For: 10.5.0.0
>
>         Attachments: derby-4008_diff.txt, derby-4008_diff_2.txt, releaseNote.html, releaseNote.html
>
>
> As part of the change for DERBY-728 we will implement UNICODEMGR which will require ACCSEC be sent in EBCDIC.  After DERBY-4004 is fixed the client should send the RDBNAM on ACCSEC only if EBCDIC conversion is possible.  This will maintain compatibility with old servers for database names that can be converted but will allow us to defer sending the database name to SECCHK so that we can send the RDBNAM in UTF-8 with new servers when UNICODEMGR is active.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.