6
0
mirror of https://github.com/FirebirdSQL/firebird-qa.git synced 2025-01-23 05:53:06 +01:00
firebird-qa/tests/functional/tabloid/test_join_transformation_007.py

119 lines
4.1 KiB
Python

#coding:utf-8
"""
ID: tabloid.join-transformation-07
TITLE: Check ability of outer join simplification.
DESCRIPTION:
For two datasources (S1, S2) and some complex query Q which has inside itself: "... left join S2 [...]"
we can replace LEFT OUTER joins inside Q with INNER if S1 and S2 are involved in INNER join with
null-rejected expression, i.e.:
S1 join ( Q left join S2 ) on null_rej (S1.b,S2.f) ==> S1 join ( Q join S2 ) on null_rej (S1.b,S2.f)
FBTEST: functional.tabloid.join_transformation_007
NOTES:
[25.11.2023] pzotov
Writing code requires more care since 6.0.0.150: ISQL does not allow to specify THE SAME terminator twice,
i.e.
set term @; select 1 from rdb$database @ set term @; - will not compile ("Unexpected end of command" raises).
"""
import pytest
from firebird.qa import *
db = db_factory(from_backup='join-transformations.fbk')
test_script = """
execute procedure sp_fill( 40, 30 );
-- ^ ^- probability of assign each field on each row to NULL (percent).
-- +- number of rows in each of tables t1...t6
commit;
execute procedure sp_recalc_idx_stat;
commit;
set list on;
set term ^;
execute block returns(result varchar(50)) as
begin
select result
from sp_run(
---------------------- Query-1 (not simplified)
-- NB: we have to make "padding" of null literals up to 6 fields
-- if query returns less columns:
'select a.id, b.id, c.id, d.id, e.id, f.id
from t1 a
left join
(t2 b ------------------------------------------------------ source_1
join
(t3 c
left
join (t4 d
left
join (t5 e
left
join t6 f ----------------------------- source_2
on e.y=f.z
) on d.x = e.y and f.y = d.z
) on c.y = e.z
) on c.u = d.w
) on b.x = f.z'
-- ^-----^--------------------- columns from source_1 and source_2 participates here in null-rejecting expr.
,
---------------------- Query-2 (simplified and we assume that it ALWAYS produces the same result as Q1)
'select a.id, b.id, c.id, d.id, e.id, f.id
from t1 a
left join
(t2 b
join
(t3 c
inner
join (t4 d
inner
join (t5 e
inner
join t6 f
on e.y=f.z
) on d.x = e.y and f.y = d.z
) on c.y = e.z
) on c.u = d.w
) on b.x = f.z'
, 0 ------------------------------------ nr_total: when 0 then do NOT run sp_fill because we already do have data for checking
) into result;
suspend;
if ( result not containing 'Passed' ) then
-- this context variable serves as 'flag' to show
-- problematic data (see following EB):
rdb$set_context('USER_SESSION', 'FAULT', '1');
end
^
execute block returns( failed_on varchar(255) ) as
begin
-- When queries are NOT equal on some data then we have to output
-- rows from all tables in order to reproduce this trouble later:
if ( rdb$get_context('USER_SESSION', 'FAULT') = '1' ) then
begin
for
select dml from sp_show_data
into failed_on
do
suspend;
end
end
^
set term ;^
"""
act = isql_act('db', test_script)
expected_stdout = """
RESULT Passed.
"""
@pytest.mark.version('>=3.0')
def test_1(act: Action):
act.expected_stdout = expected_stdout
act.execute(combine_output = True)
assert act.clean_stdout == act.clean_expected_stdout