Firebird 2 Bug Fixes
Firebird 2 Bug Fixes
Firebird 2 Bug Fixes
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
~ ~ ~<br />
Optimizer<br />
<strong>Firebird</strong> 2 <strong>Bug</strong> <strong>Fixes</strong><br />
(CORE-2078) The optimizer always had some trivial heuristics to estimate the effective stream selectivity,<br />
even if no indices could be used for the retrieval. This code missed being migrated into the ODS11 optimizer<br />
logic. The effect was that join orders chosen for cases involving non-indexed predicates were likely to be ineffective.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-2053) Computed expressions may be optimized badly if used inside the RETURNING clause<br />
of the INSERT statement<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
Database Manipulation Language (DML)<br />
(CORE-2073) The implementation of expression indexes exhibited a bug whereby an incorrect result was<br />
returned when an inverted Boolean predicate was applied to test an indexed expression.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-2118) With an UPDATE OR INSERT statement, an insert would fail silently if the MATCHING<br />
operand was a subquery.<br />
fixed by A. dos Santos Fernandes<br />
~ ~ ~<br />
(CORE-1962) Incorrect extraction of MILLISECONDs:<br />
select extract(millisecond from time '01:00:10.1234')<br />
from rdb$database<br />
would return 10123 instead of 123.4.<br />
fixed by A. dos Santos Fernandes<br />
~ ~ ~<br />
Procedural Language (PSQL)<br />
(CORE-2117) Incorrect ROW_COUNT values were being returned with indexed retrieval and subqueries.<br />
fixed by A. dos Santos Fernandes<br />
30
Change language