Hmm.. interesting answer. I have thinked about and have more questions - but now it look as suppor question - sorry for continue it here.
But >> Index scan without the upper "Bitmap" node means the same as legacy ORDER. when the Bitmap will be than, it will be legacy "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. Does it mean that plan like indexed and oredered do not exists in the same time now in FB? Maybe above sample was not good as same index is "used" for filter and sort retrival. But does it mean that plan like RL ORDER PK_ROZLICZENIE INDEX (FK_SOME_OTHER_INDEX) is not possible? I mean index filter and sort by index in the same time? regards, Karol Bieniaszewski Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
