Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <849648499.1227908684637.JavaMail.jira@brutus>
Date: Fri, 28 Nov 2008 13:44:44 -0800 (PST)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3193) SQL roles: Add documentation
In-Reply-To: <30537919.1194621651207.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Thanks so much for working on this, Kim! I will be out the next 2 weeks,, but will get back
to reading the patch in detail as soon as I am back. Just some comments on the Dev guide org:

You reorg of "User authorizations" makes sense to me, abolutely. It is wrong presently, I agree.
One thing, I would suggest renaming the section:

"Setting the user authorizations for individual users" to
"Setting access for individual users" in the hope of using the work "authorization" primarily for SQL authorization
 makes this subject less confusing. I would also finish off the treatment of connection level access control before we open up the subject of SQL authorization. Maybe like this:

User authorizations 
  Setting the default connection access mode 
  Setting access for individual users 
    Read-only and full access permissions 
  Setting the SQL standard authorization mode 
    SQL standard authorization (retitle as "Using SQL standard authorization") 
  User authorization exceptions

The section "User authorization exceptions" is currently very thin, treating only exception occuring under connection level access control. Lacking SQL privileges under SQL authorization give different errors, but are not treated. It does mention (again) how to set SQL authorization. Maybe this can be removed, and the whole section moved to under "Setting access for individual user", on the same level as "Read-only and full access permissions ". That way, we coul dlater add a section on exception that one can see under SQL authorization under "Setting the SQL standard authorization mode". 

A new roles section would then also go under "Setting the SQL standard authorization mode", I presume.

> SQL roles: Add documentation
> ----------------------------
>
>                 Key: DERBY-3193
>                 URL: https://issues.apache.org/jira/browse/DERBY-3193
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>             Fix For: 10.5.0.0
>
>         Attachments: DERBY-3193.diff, DERBY-3193.stat, DERBY-3193.zip, derby3193-tmp.diff, derby3193-tmp.stat
>
>


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