On 30/09/15 00:34, Paul Vinkenoog wrote: > Alex Peshkoff wrote: > >> On 09/29/2015 03:23 PM, Dimitry Sibiryakov wrote: >>> 29.09.2015 13:21, Paul Vinkenoog wrote: >>>> So a CASCADE option would be a welcome addition for such cases. >>> Another question: how many levels should this cascade go? >>> >> Unlimited, and about it will take care existing code - like it already >> does when revoking grant option. > > Been thinking some more about the entire REVOKE beheviour. A normal REVOKE > cascades al the way. So either REVOKE ALL ON ALL should do the same (at least > by default), or the standard REVOKE's behaviour should be changed. > > Either way (but especially in the former case) a [NO] CASCADE option that can > be used with every REVOKE variant would be most welcome. > I rather put the cat among the pigeons, didn't I :-)
But if you're going to do that, it makes sense to have CASCADE take an optional argument - the number of levels to cascade down. I don't know anything about the internals, but if you make it recursive, you only need the one implementation because NO CASCADE would be the same as CASCADE 0, and if there is an argument you simply decrement it each recursive call. (And a full CASCADE you could simply pass -1 as the argument so long as the recurse tests for 0. Pick does that when searching for strings - it wasn't designed behaviour but everyone used it and it's now "standard practice that's impossible to change" :-) Cheers, Wol ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
