db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3334) UserAuthenticator class needs to define its handling of user name more clearly.
Date Wed, 10 Sep 2014 20:54:34 GMT

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

Kim Haase commented on DERBY-3334:
----------------------------------

Although the examples make it pretty clear what is going on, the terminology is imprecise
and could be tidied up.

> UserAuthenticator class needs to define its handling of user name more clearly.
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-3334
>                 URL: https://issues.apache.org/jira/browse/DERBY-3334
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0,
10.3.1.4, 10.3.2.1, 10.4.1.3
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>              Labels: derby_triage10_11
>
> Java doc for UserAuthenticator class should clearly state the input format for user name.
> Currently the javadoc uses the terms "case-insensitive authorization identifier" and
"case-sensitive authorization identifier", which is incorrect. Authorization identifiers are
always case sensitive, it's their representation as user names that has the appearance of
being case insensitive.
> Note that user names are not really case sensitive or case insensitive, non-delimited
names are upper-cased to become an authorization identifier.
> This wiki page has the SQL rules that lead to this behaviour.
> http://wiki.apache.org/db-derby/UserIdentifiers



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message