[jira] Commented: (DERBY-4522) Document SELECT statement requirements resulting from fix to DERBY-4191

["Dag H. Wanvik (JIRA)" <ji...@apache.org>]

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

Dag H. Wanvik commented on DERBY-4522:
--------------------------------------

Great to get this documented! Two comments:

-  I think this information should also be present in the GRANT statement topic, in the paragraph that describes SELECT privilege (the one that starts with "Use the SELECT privilege type to grant permission...").

- Another thing is that in this section in the GRANT topic, the privilege requirements for SELECT is described as necessary for the *SELECT statement*. Surely, they are also necessary for the *SELECT expression* (as hinted at to by the sentence mentioning subqueries in the patch's addition to rrefsqlj41360). I think it should be possible to find the required privilege information also when looking at the *SELECT expression* topic, which is the syntax form used in an INSERT statement.  If the required privilege information is also explained in the SELECT expression topic, the extra mention of subqueries would be redundant in the patch. Also, the wording should start:

"For queries that do not select a specific column from the tables involved in the SELECT statement or expression, ...."



> Document SELECT statement requirements resulting from fix to DERBY-4191
> -----------------------------------------------------------------------
>
>                 Key: DERBY-4522
>                 URL: https://issues.apache.org/jira/browse/DERBY-4522
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.4.2.0, 10.5.3.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: DERBY-4522.diff, rrefsqlj41360.html
>
>
> The SELECT statement topic needs language based on this release note:
> "Make sure that user has at least one column level select privilege or table level select privilege for queries that do not select a specific column from the tables involved in the SELECT statement. Additionally, subqueries will require that the user has necessary select privileges in order to execute it."

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