16.01.2020 10:17, liviusliv...@poczta.onet.pl wrote:
tested on WI-V3.0.5.33187 Firebird 3.0 and WI-V3.0.5.33232 Firebird 3.0
i see that my query have legacy plan like this:
PLAN (RL ORDER PK_ROZLICZENIE)
but explained plan show this
Select Expression
-> Filter
-> Table "ROZLICZENIE" as "RL" Access By ID
-> Index "PK_ROZLICZENIE" Range Scan (lower bound: 2/5,
upper bound: 3/5)
Everything is correct. Index scan without the upper "Bitmap" node means
the same as legacy ORDER.
which plan finaly engine have?
1. RL ORDER PK_ROZLICZENIE
This one.
2. RL INDEX (PK_ROZLICZENIE)
3. RL ORDER PK_ROZLICZENIE INDEX (PK_ROZLICZENIE)
The third plan was a bug in FB 2.x, it should never appear in FB3 and above.
Dmitry
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
