I don't remember why I did so but maybe it's better to allow drop sql
security for any object type and remove the wrong statement at all.

вс, 9 мая 2021 г. в 17:07, Mark Rotteveel <m...@lawinegevaar.nl>:
>
> The 'SQL SECURITY Feature' section of the Firebird 4.0 Release Notes has
> a contradictory statement. It says:
>
> """
> The property cannot be dropped but it can be changed from INVOKER to
> DEFINER and vice versa.
> """
>
> However, the syntax explicitly includes `DROP SQL SECURITY` for `ALTER
> TABLE` and `ALTER TRIGGER`.
>
> Would it be sufficient to say something like
>
> """
> The property cannot be dropped for procedures, functions and packages,
> but it can be changed from INVOKER to DEFINER and vice versa.
> """
>
> Mark
> --
> Mark Rotteveel
>
>
> Firebird-Devel mailing list, web interface at 
> https://lists.sourceforge.net/lists/listinfo/firebird-devel



-- 
Roman Simakov


Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to