New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad plan in outer joins with IS NULL clauses (dependent on order of predicates) [CORE1029] #1444
Comments
Commented by: @pcisar Fix verified, test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @pcisar Reopened to update ticket information. |
Modified by: @pcisarWorkflow: jira [ 11362 ] => Firebird [ 15369 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Submitted by: @dyemanov
Is related to QA25
create table tb1 (id int, col int);
create index tbi1 on tb1 (id);
create index tbi2 on tb1 (col);
insert into tb1 values (1, 1)
insert into tb1 values (2, 2)
insert into tb1 values (1, null)
select *
from tb1 a
left join tb1 b on http://a.id = http://b.id
where a.col is null and a.col+0 is null
--where a.col+0 is null and a.col is null
PLAN JOIN (A NATURAL, B INDEX (TBI1))
select *
from tb1 a
left join tb1 b on http://a.id = http://b.id
--where a.col is null and a.col+0 is null
where a.col+0 is null and a.col is null
PLAN JOIN (A INDEX (TBI2), B INDEX (TBI1))
The bug is inside OPT_compile(), related to handling of missingStack.
Commits: 4bdeba3 c239258
The text was updated successfully, but these errors were encountered: