Skip to content
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

Tricky index names can defeat the parsing logic when generating a human readable plan [CORE2508] #1092

Closed
firebird-issue-importer opened this issue Jun 13, 2009 · 4 comments

Comments

@firebird-issue-importer

Submitted by: Claudio Valderrama C. (robocop)

SQL> select 1 from rdb$relations where rdb$relation_id in (0,1,2);
PLAN (RDB$RELATIONS INDEX (RDB$INDEX_1, RDB$INDEX_1, RDB$INDEX_1))

so far so good, but

SQL> create table t(a int not null);
SQL> create index "abc(" on t(a);
SQL> select * from t where a in (0, 1, 2);
PLAN (T INDEX (abc(abc(abc())

Hopefully, nobody that passed a sanity check would create such names!

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 2, 2011

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

assignee: Dmitry Yemanov [ dimitr ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Feb 14, 2011

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 18, 2016

Modified by: @pavel-zotov

QA Status: No test

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 31, 2016

Modified by: @pavel-zotov

status: 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