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 />
<strong>Firebird</strong> 2 <strong>Bug</strong> <strong>Fixes</strong><br />
(CORE-2858) Memory could be trashed when raising some exceptions to signal failed security checks.<br />
fixed by C. Valderrama C.<br />
~ ~ ~<br />
(CORE-2856) A non-NULL key in a unique index could not be found when the key was removed<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-2833) Changing data that affected an expression index would fail if that data contained references<br />
to null date fields.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-2827) The Prepare for complex interrelated metadata, where many triggers were indirectly involved<br />
in the operation being prepared, was very slow.<br />
fixed by D. Yemanov<br />
(CORE-2826) Join condition would fail for UTF-8 databases.<br />
fixed by A. dos Santos Fernandes<br />
~ ~ ~<br />
(CORE-2822) The error “no current row for fetch operation” was being thrown when a subquery included<br />
a non-trivial derived table.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-2820) Queries with PLAN ORDER were exhibiting small memory leaks as a side effect of an<br />
earlier, major fix.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-2815) Tidy-up of a logic condition that could cause the page inventory page to be marked for<br />
change after it was already changed.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-2785) An improperly handled BLOB transliteration problem showed up under specific conditions,<br />
viz., where an input argument string in single-byte Cyrillic text, for storing as COMMENT with an object<br />
definition, overstepped the maximum 64 KB size of a non-initial BLOB segment when transliterated. Its surplus<br />
14
Change language