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 "Laura Stewart (JIRA)" <de...@db.apache.org> on 2006/08/04 22:11:15 UTC

[jira] Commented: (DERBY-1646) Documentation to address Grant/Revoke Authorization for views/triggers/constraints/routines(DERBY-1330)

    [ http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12425841 ] 
            
Laura Stewart commented on DERBY-1646:
--------------------------------------

In Derby-1330 I asked some questions about the properties in the spec AuthorizationMOdelFroDerbySQLStandardAuthorizationV2.html.

I need some further clarification on these 2 properties and how we refer to them:

derby.database.defaultConnectionMode 
derby.database.sqlAuthorization

Questions:
1. If the derby.database.defaultConnectionMode property is not set, the default authorization is fullAccess.  The user does not have to set anything, correct?

2. Does the derby.database.sqlAuthorization have a default setting?

3. Is it important for the documentation to distingush between the "Derby Authorization model" and the "Derby SQL Standard Authorization model"?
Are these the terms that should be externalized in the documentation?

Thanks!



> 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