Firebird 2 Bug Fixes

Firebird 2.1.2
Firebird 2 Bug Fixes
The following bug fixes/reversions have been applied since the release of v.2.1.1:
Core Engine
(CORE-2329) Discovered a significant source of performance degradation in comparison with V.1.5.
fixed by D. Yemanov
~ ~ ~
(CORE-2326) Committing a new user object (a view, for example) caused an access violation if a
user-defined trigger had been applied to the system table RDB$RELATIONS.
It should be noted that no Firebird server version either supports, or retains after a backup and restore, any
user-defined trigger on a system table. The strong recommendation against defining such triggers remains. The
fix recognises one way that user interference with system tables can compromise internal operations and disarms
it.
The ability to define “DDL triggers” through the regular DDL mechanisms is on the drawing board for V.3.
fixed by D. Yemanov
~ ~ ~
(CORE-2242) The engine was incorrectly populating integer containers in the blob parameter buffer (BPB)
with integers in machine-local format, causing errors on Big Endian platforms.
fixed by A. Peshkov
~ ~ ~
(CORE-2241) If an ALTER TABLE ALTER COLUMN.. operation was performed on a table in the course
of a bulk insert operation, minor index corruption could occur causing subsequent queries to return the wrong
number of records. The bug was traced to legacy code in BTR\compress_root().
fixed by V. Khorsun
~ ~ ~
(CORE-2227) Problems were occurring in some environments when creating triggers that referred to
column names with accented characters.
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-2222) Storing a text blob with a transliteration blob filter could cause an access violation in
the engine.
fixed by V. Khorsun
26