Broken optimization for the stored dbkeys
-----------------------------------------
Key: CORE-4038
URL: http://tracker.firebirdsql.org/browse/CORE-4038
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 2.5.2, 2.5.1, 2.5.0
Reporter: Dmitry Yemanov
Test case:
create table t (dbkey char(8) character set octets);
create index it on t (dbkey);
select * from t as t1
left join t as t2 on t2.dbkey = t1.rdb$db_key
-- expected plan:
PLAN JOIN (T1 NATURAL, T2 INDEX (IT))
-- actual plan:
PLAN JOIN (T1 NATURAL, T2 NATURAL)
This is a regression introduced with CORE-2550 when a separate internal
datatype was created for dbkeys.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
