[ http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12425935 ] Satheesh Bandaram commented on DERBY-1646: ------------------------------------------
I think we need to document "Derby Authorization mode" and "SQL standard authorization mode" in Derby. That is we need to externalize the modes, as enabling GRANT/REVOKE while allows fine grained access, it also takes away something that used to work before. (like ability to create any number of schemas or ability to create objects in other schemas etc.) I think it is important to be consistant about defaultConnectionMode that controls access mode and sqlAuthorization that enables SQL standard authorization. Though both properties can interact with each other, I think, it may be best to document each independently and then may be have a section that covers what happens when both are set. I will reply to Laura's earlier post in another comment. > 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
