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-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 Fri, 19 Oct 2007 17:54:50 GMT

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

Kim Haase commented on DERBY-2914:
----------------------------------

That looks fine -- actually you could shorten it even further to say "for the specified user"
-- I think that would be clear.

I think I understand what that last phrase means (I was tangling with connection modes for
DERBY-1823): I think, for example, if you set the default connection mode for the database
to NO_ACCESS, created a user, and did not add that user to the list of people with full access
or read-only access, the function would return NO_ACCESS for that user. Someone please correct
me if I'm mistaken here. (The database properties you set are described in Tuning Derby, along
with all other Derby properties.)

Whether the current phrasing conveys that meaning I'm not sure. It might be more correct to
change "and factors in" to "factoring in". Or "taking into account". I don't think "based
on" or "depending on" would be correct -- that would oversimplify what's going on.


> 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.5, 10.3.2.0, 10.4.0.0
>
>         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