Tricky index names can defeat the parsing logic when generating a human readable plan [CORE2508] #1092
Labels
affect-version: 1.5.4
affect-version: 1.5.5
affect-version: 1.5.6
affect-version: 2.0.0
affect-version: 2.0.1
affect-version: 2.0.2
affect-version: 2.0.3
affect-version: 2.0.4
affect-version: 2.0.5
affect-version: 2.1.0
affect-version: 2.1.1
affect-version: 2.1.2
affect-version: 2.1.3
affect-version: 2.5 Alpha 1
affect-version: 2.5 Beta 1
affect-version: 2.5 Beta 2
affect-version: 2.5.0
component: engine
fix-version: 3.0 Alpha 1
priority: minor
qa: done successfully
type: bug
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!
The text was updated successfully, but these errors were encountered: