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 Wed, 16 Apr 2008 23:08:20 GMT

Found this quote in DERBY-1330's attachment
"AuthorizationModelForDerbySQLStandardAuthorizationV2.html" which
explains the absence of an explicit CASCADE syntax in Derby:

> Derby SQL Standard Authorization will support SQL2003 CASCADE behavior
> on revoke(with the exception of revoke routine, where RESTRICT
> behavior will be supported and the RESTRICT will be a mandatory
> keyword on the revoke routine syntax). Although CASCADE will be the
> default behavior of Derby SQL Standard Authorization's revoke
> statement, syntactically, there will be no way to specify the keyword
> CASCADE on the revoke syntax. 
> This decision was based on the fact that none of the other major
> databases, including Oracle, SQL Server, DB2, MySQL provide a way to
> specify RESTRICT/CASCADE behavior on their revoke statement
> syntax).*

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


View raw message