Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <18483376.1154793735809.JavaMail.jira@brutus>
Date: Sat, 5 Aug 2006 09:02:15 -0700 (PDT)
From: "Daniel John Debrunner (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1646) Documentation to address
 Grant/Revoke Authorization for
 views/triggers/constraints/routines(DERBY-1330)
In-Reply-To: <26339948.1154713813839.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12425972 ] 
            
Daniel John Debrunner commented on DERBY-1646:
----------------------------------------------

I like it when Satheesh wrote:
"I think it is important to be consistant about defaultConnectionMode that controls access mode and sqlAuthorization that enables SQL standard authorization"

Use "authorization" for grant/revoke and "access " for the connection full/read/none access., maybe even clarify by calling it "connection access".

This would need to follow through to Satheesh's re-write in the comment above (dated 5 Aug 12:14am)
http://issues.apache.org/jira/browse/DERBY-1646#action_12425937

E.g.
Replace:
The derby.database.defaultConnectionMode property controls the default authorization when users connect to the database. 
with
The derby.database.defaultConnectionMode property controls the default connection access when users connect to the database. 

Maybe the whole first section could be re-written to not have defaultConnectionMode refer to database objects at all, if one just thinks about connection access then it would be described by:

     none - The user is not allowed to make a connection to the database
     read-only - the user's connection is in read-only mode and can not modify the database in any way .   Connecttion.isReadOnly will return true and
              Connection.setReadOnly(false) will throw an exception
      fullAccess - The connection is in read-write mode, Connecttion.isReadOnly returns false, Connection.setReadOnly() may be used freely.


> Documentation to address Grant/Revoke Authorization for views/triggers/constraints/routines(DERBY-1330)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1646
>                 URL: http://issues.apache.org/jira/browse/DERBY-1646
>             Project: Derby
>          Issue Type: New Feature
>          Components: Documentation
>    Affects Versions: 10.2.0.0
>            Reporter: Mamta A. Satoor
>         Assigned To: Laura Stewart
>
> Creating a separate jira entry for documentation of Grant/Revoke Authorization for views/triggers/constraints/routines(Engine changes are going as part of DERBY-1330).
> Will link this jira entry to DERBY-1330

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira