6
0
mirror of https://github.com/FirebirdSQL/firebird-qa.git synced 2025-01-22 21:43:06 +01:00
firebird-qa/tests/bugs/core_4054_test.py

126 lines
3.8 KiB
Python

#coding:utf-8
"""
ID: issue-4382
ISSUE: 4382
TITLE: role not passed on external execute stmt
DESCRIPTION:
JIRA: CORE-4054
FBTEST: bugs.core_4054
"""
import pytest
from firebird.qa import *
db = db_factory()
test_script = """
set wng off;
-- Drop old account if it remains from prevoius run:
set term ^;
execute block as
begin
begin
execute statement 'drop user tmp$c4054' with autonomous transaction;
when any do begin end
end
end
^
set term ;^
commit;
create user tmp$c4054 password '123';
commit;
revoke all on all from tmp$c4054;
commit;
create table test(id int);
commit;
insert into test(id) values(789654123);
commit;
set term ^;
execute block as
begin
execute statement 'drop role r4054';
when any do
begin
end
end
^
set term ;^
commit;
create role r4054;
commit;
grant select on test to role r4054;
commit;
grant r4054 to tmp$c4054;
commit;
set list on;
set term ^;
execute block returns (who_am_i varchar(30), whats_my_role varchar(30), what_i_see int) as
declare v_dbname type of column mon$database.mon$database_name;
declare v_usr rdb$user = 'tmp$c4054';
declare v_pwd rdb$user = '123';
declare v_role type of column rdb$roles.rdb$role_name;
begin
v_dbname = 'localhost:' || rdb$get_context('SYSTEM', 'DB_NAME');
--######################
v_role = upper('r4054'); -- !!! ACHTUNG !!! ROLE NAME MUST BE ALWAYS PASSED IN UPPER CASE !!!
--######################
-- Explanation can be seen here (russian):
-- http://www.sql.ru/forum/actualutils.aspx?action=gotomsg&tid=1074439&msg=15494916
for
execute statement 'select current_user, current_role, t.id from test t'
on external v_dbname
as user v_usr
password v_pwd
role v_role -- ####### ONCE AGAIN: ALWAYS PASS ROLE NAME IN *UPPER* CASE! ##########
into who_am_i, whats_my_role, what_i_see
do
suspend;
end
^
set term ;^
commit;
-- ||||||||||||||||||||||||||||
-- ###################################||| FB 4.0+, SS and SC |||##############################
-- ||||||||||||||||||||||||||||
-- If we check SS or SC and ExtConnPoolLifeTime > 0 (config parameter FB 4.0+) then current
-- DB (bugs.core_NNNN.fdb) will be 'captured' by firebird.exe process and fbt_run utility
-- will not able to drop this database at the final point of test.
-- Moreover, DB file will be hold until all activity in firebird.exe completed and AFTER this
-- we have to wait for <ExtConnPoolLifeTime> seconds after it (discussion and small test see
-- in the letter to hvlad and dimitr 13.10.2019 11:10).
-- This means that one need to kill all connections to prevent from exception on cleanup phase:
-- SQLCODE: -901 / lock time-out on wait transaction / object <this_test_DB> is in use
-- #############################################################################################
delete from mon$attachments where mon$attachment_id != current_connection;
commit;
-- Do not forget about cleanup - remember that other tests can query sec$users or run `show users`!
drop user tmp$c4054;
commit;
"""
act = isql_act('db', test_script)
expected_stdout = """
WHO_AM_I TMP$C4054
WHATS_MY_ROLE R4054
WHAT_I_SEE 789654123
"""
@pytest.mark.version('>=3')
def test_1(act: Action):
act.expected_stdout = expected_stdout
act.execute()
assert act.clean_stdout == act.clean_expected_stdout