14.02.2022 22:40, Roman Simakov wrote:
I don't remember exactly why we decided to make it nullable. I suppose
for more backward compatibility. If a client doesn't use it it will be
NULL everywhere.
Maybe the idea was to distinguish between legacy databases (restored
without SQL SECURITY) and
I don't remember exactly why we decided to make it nullable. I suppose
for more backward compatibility. If a client doesn't use it it will be
NULL everywhere.
So in fact it can be NULL physically. But logically only two options
make sense. NULL is considered as legacy, i.e. INVOKER.
Thus you are
You say it cannot be NULL, yet you say the "initial NULL". Looks very inconsist
to me. Now for INVOKER there's 2 possible values. Yet one can't ever be set by
user.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On Mon, Feb 14, 2022, at 15:22, Roman Simakov wrote:
> It's the default for
It's the default for a database. It cannot be NULL. Initial NULL means INVOKER.
пн, 14 февр. 2022 г. в 16:43, Jiří Činčura :
>
> Hi *,
>
> How can I drop SQL SECURITY on database, aka setting the RDB$SQL_SECURITY
> column back to "null"?
>
> --
> Mgr. Jiří Činčura
>
Hi *,
How can I drop SQL SECURITY on database, aka setting the RDB$SQL_SECURITY
column back to "null"?
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
