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] Reopened: (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, 08 Oct 2007 12:31:51 GMT

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

John H. Embretsen reopened DERBY-2914:
--------------------------------------


Reopening this issue because errors in the documentation of 
SYSCS_UTIL.SYSCS_SET_USER_ACCESS and
SYSCS_UTIL.SYSCS_GET_USER_ACCESS
have been uncovered in issue DERBY-3095.

Regarding the SYSCS_UTIL.SYSCS_SET_USER_ACCESS system procedure,
http://db.apache.org/derby/docs/dev/ref/rrefsetuseraccess.html:
****************************
Valid values for CONNECTION_PERMISSION should be
   FULLACCESS
   READONLYACCESS 
   NULL

Also, there is a missing space in the description of FULL/FULLACCESS: "isderby.database.fullAccessUsers."

I also think it would be good to show (in an example) how to use the NULL value in this context,
because it must be used differently (i.e. no quotes) than the two other values. For example:

CALL SYSCS_UTIL.SYSCS_SET_USER_ACCESS ('EVE', NULL);


Regarding the SYSCS_UTIL.SYSCS_GET_USER_ACCESS system procedure,
http://db.apache.org/derby/docs/dev/ref/rrefgetuseraccess.html:
****************************

This is documented as a Built-in system procedure, but should rather be documented as a Built-in
system function (see for example the SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY system function,
http://db.apache.org/derby/docs/dev/ref/rrefgetdbpropfunc.html).

The value that is returned by this procedure is either FULLACCESS, READONLYACCESS, NOACCESS
or NULL.
I don't know when the value NULL would be returned, so perhaps this should be explained as
well?

The example should use VALUES, not CALL (which fails), e.g.:
VALUES SYSCS_UTIL.SYSCS_GET_USER_ACCESS ('ALICE')


> 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.4.0.0
>
>         Attachments: derby2914_1.diff, rrefemptystmtcache.html, rrefemptystmtcache.html,
rrefgetuseraccess.html, rrefgetuseraccess.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