upport] Optimize query for date ranges
Niko,
> the execution is currently not the problem, because the number of
> records is too small.
>
> I have the impression that the first query looks for DATUM >= x and
> the second one for DATUM <= y and finally delivers the number of
On Tue, Oct 13, 2015 at 3:47 PM, 'Parzival' parzival1...@gmx.at
[firebird-support] wrote:
> Hello Thomas,
>
> the result set contains 3 record for criteria.
>
> Records DATUM >= '5.10.2015' = 102
> Records DATUM <= '11.10.2015' = 26
>
> It seems that both
Hi,
the execution is currently not the problem, because the number of records is
too small.
I have the impression that the first query looks for DATUM >= x and the
second one for DATUM <= y and finally delivers the number of records that is
included in both result sets.
My main interesst is to
Hello,
there are two indices on the field DATUM: One ascending, the other one
descending.
Plan:
PLAN (A INDEX (IDX_ARBEITSEINTEILUNG1))
Adapted plan:
PLAN (A INDEX (IDX_ARBEITSEINTEILUNG1))
Niko
Von: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]