db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: Rationale for REVOKE EXECUTE.. RESTRICT vs. REVOKE <role>
Date Thu, 17 Apr 2008 00:05:38 GMT
Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:

> RESTRICT for revoke routine is not not given a rationale here,
> though. Looking further...

I see this version of DB2 also requires RESTRICT:

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/r0007700.htm

So, possibly, the rationale for the Derby behavior here is merely DB2
compatibility.

However, some docs for DB2 makes it optional:

http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db29.doc.sqlref/db2z_sql_revokefunctionorprocedureprivileges.htm

It seems the initial specification for GRANT/REVOKE had mandatory
RESTRICT for execution privilege, no rationale given (DERBY-464):

https://issues.apache.org/jira/secure/attachment/12323047/grantRevokeSpec.html

Dag

Mime
View raw message