Firebird 2 Bug Fixes
Firebird 2 Bug Fixes
Firebird 2 Bug Fixes
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
fixed by A. dos Santos Fernandes<br />
~ ~ ~<br />
<strong>Firebird</strong> 2 <strong>Bug</strong> <strong>Fixes</strong><br />
(CORE-3464) A dirty page could be written without releasing (or downgrading) its page lock. The result<br />
would be a bugcheck indicating either “lock denied” or “lock conversion denied”.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-3418) A database trigger created as INACTIVE would actually be created active.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-3409) A segmentation fault could occur after upgrading from v.2.1.3 to v.2.1.4.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-3397) The intl and trace libraries had unresolved symbols.<br />
fixed by A. Peshkov<br />
~ ~ ~<br />
(CORE-3394) A failed attempt to violate a unique constraint could leave a superfluous “lock conflict”<br />
error in the status vector.<br />
fixed by V. Khorsun<br />
~ ~ ~<br />
(CORE-3355) DATE and TIMESTAMP would be compared wrongly if an index was used.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-3353) A predicate (blob_field LIKE ?) would describe the parameter as VARCHAR(30) rather<br />
than as BLOB.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-3335) Internal wrapping was occurring for the multi-byte blob SUBSTRING function and its<br />
boundary arguments, producing wrong results.<br />
fixed by D. Yemanov<br />
~ ~ ~<br />
(CORE-3296) A “context already in use” error would occur when the simple CASE function had an<br />
operand that was a subquery.<br />
6
Change language