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 "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2006/07/24 09:05:15 UTC
[jira] Updated: (DERBY-1579) Remove SYS.SYSREQUIREDPERM from Derby
10.2. This was added for Grant Revoke functionality
[ http://issues.apache.org/jira/browse/DERBY-1579?page=all ]
Mamta A. Satoor updated DERBY-1579:
-----------------------------------
Summary: Remove SYS.SYSREQUIREDPERM from Derby 10.2. This was added for Grant Revoke functionality (was: Remove SYS.SYSREQUIREDPERMS from Derby 10.2. This was added for Grant Revoke functionality)
> Remove SYS.SYSREQUIREDPERM from Derby 10.2. This was added for Grant Revoke functionality
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-1579
> URL: http://issues.apache.org/jira/browse/DERBY-1579
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> With the Grant Revoke functionality. Derby engine needs to keep track of view/constraint/trigger's dependencies on various privileges. SYS.SYSREQUIREDPERM table was added for this purpose. But these depdencies can be mantained using the existing Dependency Manager. I have done quite a bit of work using Dependency Manager for Grant Revoke and do not see a need for SYS.SYSREQUIREDPERM. Before 10.2 release, we should drop SYS.SYSREQUIREDPERM from the Derby code and update the Grant/Revoke functional spec accordingly.
--
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