[
https://issues.apache.org/jira/browse/DERBY-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067100#comment-13067100
]
Dag H. Wanvik commented on DERBY-5329:
--------------------------------------
The answer to the first question is "yes". On number two, technically, SQL
authorization can be enabled without authentication in Derby, but it is rather
pointless since all users can pretend to be anyone, including the DBO. I.e.
authentication can be meaningfully used without SQL authorization, but the
opposite is not true. I guess our present wording is a bit verbose (and
technically wrong: for execution privileges one does need to at least *pretend*
to be the dbo - by connecing as dbo), it makes more sense. So I suggest we
continue to use what we currently have: "If authentication and SQL
authorization are both enabled, ...".
> Document who is allowed to run which system procedures/functions.
> -----------------------------------------------------------------
>
> Key: DERBY-5329
> URL: https://issues.apache.org/jira/browse/DERBY-5329
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Fix For: 10.8.1.6, 10.9.0.0
>
> Attachments: DERBY-5329.diff, DERBY-5329.stat, DERBY-5329.zip,
> rrefaltertablecompress.html, rrefstorejarinstall.html
>
>
> The 5th functional spec attached to DERBY-464 contains a table describing
> which system procedures/functions can only be run by the DBO and which can be
> run by everyone. I can't find this information in our user guides. It would
> be good to copy this information into the Reference Guide topics for each of
> these procedures/functions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
