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
The new FB4 SQL SECURITY feature doesn't seem to work properly when used together with monitoring tables (copied from CORE2557 comments):
The following procedure created by SYSDBA returns all connections when run by SYSDBA. But when run by an ordinary user, it sees only that user's connections.
CREATE PROCEDURE TEST
RETURNS (CONCNT INTEGER)
SQL SECURITY DEFINER
AS
BEGIN
select count (*) from mon$attachments into :CONCNT;
suspend;
END^
Submitted by: michalk1 (michalk1)
The new FB4 SQL SECURITY feature doesn't seem to work properly when used together with monitoring tables (copied from CORE2557 comments):
The following procedure created by SYSDBA returns all connections when run by SYSDBA. But when run by an ordinary user, it sees only that user's connections.
CREATE PROCEDURE TEST
RETURNS (CONCNT INTEGER)
SQL SECURITY DEFINER
AS
BEGIN
select count (*) from mon$attachments into :CONCNT;
suspend;
END^
GRANT EXECUTE ON PROCEDURE TEST TO PUBLIC^
Commits: bb3c2e9
The text was updated successfully, but these errors were encountered: