You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have created a user TEST, using which I can access the system tables:
SQL> SELECT 1 FROM rdb$database;
CONSTANT
============
1
I have granted ALL PRIVILEGES, including creating views to this user. For instance:
SQL> create view v as select 1 a from t_book;
SQL> select * from v;
A
============
1
1
1
1
SQL> rollback;
SQL> drop view v;
But when I want to create a view that selects from the system table, something goes wrong:
SQL> create view v as select 1 a from rdb$database;
Statement failed, SQLSTATE = 28000
unsuccessful metadata update
-CREATE VIEW V failed
-no permission for SELECT access to TABLE/VIEW RDB$DATABASE
From a high level, I would say that this is a bug, right?
The problem fixed was wider than one noticed by Lukas - non-DBA user could not create any view containing some other table/view. That was due to the check of database security class removed in other places but kept in view creation check. Database security class is now used for database-level DDL rights control and makes no sense in view creation for individual tables.
Submitted by: Lukas Eder (lukas.eder)
I have created a user TEST, using which I can access the system tables:
SQL> SELECT 1 FROM rdb$database;
============
1
I have granted ALL PRIVILEGES, including creating views to this user. For instance:
SQL> create view v as select 1 a from t_book;
SQL> select * from v;
============
1
1
1
1
SQL> rollback;
SQL> drop view v;
But when I want to create a view that selects from the system table, something goes wrong:
SQL> create view v as select 1 a from rdb$database;
Statement failed, SQLSTATE = 28000
unsuccessful metadata update
-CREATE VIEW V failed
-no permission for SELECT access to TABLE/VIEW RDB$DATABASE
From a high level, I would say that this is a bug, right?
Commits: aa55704 FirebirdSQL/fbt-repository@4e5cd0c
The text was updated successfully, but these errors were encountered: