You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2010/02/04 15:48:27 UTC

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

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

Kim Haase resolved DERBY-4522.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.6.0.0
    Issue & fix info:   (was: [Patch Available])

Thanks, Dag!

Committed patch DERBY-4522-2.diff to documentation trunk at revision 906505. 


> 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
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY-4522-2.diff, DERBY-4522.diff, DERBY-4522.stat, DERBY-4522.zip, 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.