db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented
Date Mon, 22 Oct 2007 07:59:51 GMT

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

johnemb edited comment on DERBY-2914 at 10/22/07 12:59 AM:
---------------------------------------------------------------------

I believe Kim is right about "factors in the default connection mode". In my own words: If
no connection access permission has been set explicitly for a specific user, then the user
inherits the default permission - and the SYSCS_UTIL.SYSCS_GET_USER_ACCESS system function
takes this into account. 

The default permission (also known as the default connection mode) may be set by using the
derby.database.defaultConnectionMode property, and is "fullAccess" by default (which has the
same meaning as "FULLACCESS" in this context - it is unfortunate that different parts of the
documentation refers to the same permission values with different casing, since the user may
wonder if  this is the same value or not...). http://db.apache.org/derby/docs/dev/tuning/rtunproper24846.html
.

A link to the manual page for derby.database.defaultConnectionMode would thus be nice, but
it's no requirement.

The suggested phrasing "If no permission is set for the user, the setting for the default
connection mode is returned." is OK. Do you think the following is clearer, or more confusing?

"If no permission is set explicitly for the user, the user's access permission is the value
of the default connection mode".

I think another confusing element is that several different terms are used to describe the
same thing in this context: "connection authorization", "connection mode", "access permission"
and "access permissions", but that's a bigger issue which involves more than just these manual
pages.

      was (Author: johnemb):
    I believe Kim is right about "factors in the default connection mode". In my own words:
If no connection access permission has been set explicitly for a specific user, then the user
inherits the default permission - and the SYSCS_UTIL.SYSCS_GET_USER_ACCESS system function
takes this into account. 

The default permission (also known as the default connection mode) may be set by using the
derby.database.defaultConnectionMode property, and is "noAccess" by default (which has the
same meaning as "NOACCESS" in this context - it is unfortunate that different parts of the
documentation refers to the same permission values with different casing, since the user may
wonder if  this is the same value or not...). http://db.apache.org/derby/docs/dev/tuning/rtunproper24846.html
.

A link to the manual page for derby.database.defaultConnectionMode would thus be nice, but
it's no requirement.

The suggested phrasing "If no permission is set for the user, the setting for the default
connection mode is returned." is OK. Do you think the following is clearer, or more confusing?

"If no permission is set explicitly for the user, the user's access permission is the value
of the default connection mode".

I think another confusing element is that several different terms are used to describe the
same thing in this context: "connection authorization", "connection mode", "access permission"
and "access permissions", but that's a bigger issue which involves more than just these manual
pages.
  
> new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS,
SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2914
>                 URL: https://issues.apache.org/jira/browse/DERBY-2914
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.3.1.4, 10.4.0.0
>            Reporter: Myrna van Lunteren
>            Assignee: Laura Stewart
>             Fix For: 10.3.1.4
>
>         Attachments: derby2914_1.diff, derby2914_2.diff, rrefemptystmtcache.html, rrefemptystmtcache.html,
rrefgetuseraccess.html, rrefgetuseraccess.html, rrefgetuseraccess.html, rrefsetuseraccess.html,
rrefsetuseraccess.html, rrefsetuseraccess.html
>
>
> With DERBY-2772 and DERBY-2735 3 new procedures
> SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS and SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE()
>  were created; they need to be documented in the reference manual.

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


Mime
View raw message