вс, 9 мая 2021 г. в 19:04, Mark Rotteveel <m...@lawinegevaar.nl>: > > On 09-05-2021 17:58, Roman Simakov wrote: > > I guess this was the reason not to implement it. But objects inherit > > SQL SECURITY from the database and it might be useful to drop sql > > security in order to use database default. > > Does that mean that the ALTER DATABASE SET DEFAULT SQL SECURITY <type> > influences all objects without an explicit SQL SECURITY property?
I've checked. It influences tables, functions and procedures. Triggers inherit it from tables (which already have it inherited from DB). I'm afraid packages do not inherit and it's probably a fault as well. > I had assumed it would specify the default for creating a new object > (similar as SET DEFAULT CHARACTER SET). Can you confirm that assumption > was wrong? Yes. The assumption was wrong. SQL SECURITY DEFINER is default in SQL STANDARD. ALTER DATABASE SET DEFAULT SQL SECURITY DEFINER makes behaviour standard. -- Roman Simakov Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
