[
https://issues.apache.org/jira/browse/DERBY-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665944#action_12665944
]
kmarsden edited comment on DERBY-4008 at 1/21/09 12:03 PM:
-----------------------------------------------------------------
Attached is a patch for this issue. It changes the client to not send the
RDBNAM on ACCSEC if EBCDIC conversion is not possible. For a 10.5 client to
10.5 server there is no behavior change except that the exception for
conversion exception comes a bit later (on SECCHK) instead of ACCSEC.
As discussed, for 10.5 client talking to older servers, this will cause a
change in the exception when trying to connect with a non-convertible database
name. Users will instead get a SYTAXRM with a chained conversion exception. I
will backport DERBY-4004 to mitigate this and also make a release note for this
issue.
Also added tests for connection attempts with Chinse database name, user and
password with DriverManager, Simple DataSource, XADataSource, and
ConnectionPoolDataSource.
Running tests now.
was (Author: kmarsden):
Attached is a patch for this issue. It changes the client to not send the
RDBNAM on ACCSEC if EBCDIC conversion is not possible. For a 10.5 client to
10.5 server there is no behavior change except that the exception for
conversion comes a bit later (on SECCHK) instead of ACCSEC.
As discussed, for 10.5 client talking to older servers, this will cause a
change in the exception when trying to connect with a non-convertible database
name. Users will instead get a SYTAXRM with a chained conversion exception. I
will backport DERBY-4004 to mitigate this and also make a release note for this
issue.
Also added tests for connection attempts with Chinse database name, user and
password with DriverManager, Simple DataSource, XADataSource, and
ConnectionPoolDataSource.
Running tests now.
> 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
> Attachments: derby-4008_diff.txt
>
>
> 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.
