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
Join using RDB$DB_KEY produce NATURAL plan [CORE3997] #4329
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA 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: @aafemt
Duplicates CORE1295
Following script shows plan JOIN (T_KEY NATURAL, T NATURAL) instead of JOIN (T_KEY NATURAL, T INDEX())
create table t (f integer);
create table t_key (k char(8) character set octets);
commit;
set term ^;
execute block as
declare variable i integer=100000;
begin
While (i>0) do
begin
insert into t values (:i);
i = i-1;
end
end^
set term ;^
commit;
insert into t_key select rdb$db_key from t where f=1;
commit;
set plan on;
select f from t join t_key on t.rdb$db_key=t_key.k;
The text was updated successfully, but these errors were encountered: