Firebird Documentation Index → Firebird 2.5 Release Notes → Bugs Fixed → Firebird 2.5.5 Release |
The following improvements and bug fixes were reported as fixed prior to the v.2.5.5 release:
(CORE-4978)
IMPROVEMENT: Improve validation and fixup
of lost data pages
Implemented by R. Simakov
~ ~ ~
(CORE-4943)
Casting DATE to string would break in Dialect 1
in the presence a domain with a CHECK constraint
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-4937)
A view or subquery with UNION would not
use a computed index
fixed by D. Yemanov
~ ~ ~
(CORE-4927)
IIF function was preventing the
condition from being pushed into the union for better optimization
fixed by D. Yemanov
~ ~ ~
(CORE-4921)
Predicate IS [NOT] DISTINCT FROM was not
being pushed into unions/aggregates, resulting in sub-optimal plans
fixed by D. Yemanov
~ ~ ~
(CORE-4917)
ALTER DOMAIN ... TO <new_name>
would allows the <new_name> to be specified in the same pattern as domains
generated by the system, i.e., matching to 'RDB$[[:DIGIT:]]*'
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-4909)
MERGE / HASH JOINs would produce incorrect
results when VARCHAR join keys differed only by trailing spaces
fixed by D. Yemanov
~ ~ ~
(CORE-4908)
The server could hang on simultaneous
connection to the Services API and a database
fixed by A. Peshkov
~ ~ ~
(CORE-4905)
An invalid internal BLR filter
conversion was detected
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-4904)
Index corruption could occur while
inserting data into a long-key-indexed field
fixed by V. Khorsun
~ ~ ~
(CORE-4867)
Preparing a query with a PLAN clause
in a CTE could crash the server
fixed by D. Yemanov
~ ~ ~
(CORE-4830)
A memory leak was detected in
Superserver
fixed by V. Khorsun
~ ~ ~
(CORE-4822)
MERGE JOIN could be used for expressions
involving RDB$DB_KEY
fixed by D. Yemanov
~ ~ ~
(CORE-4809)
MERGE JOIN was not being used for
more than two streams if they were joined via USING/NATURAL clauses
fixed by D. Yemanov
~ ~ ~
(CORE-4789)
Timestamps could be cast to strings
that were beyond the valid range for VARCHAR
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-4786)
The full text of the problem value
was not being returned in the message “Problematic key value (attempting to insert duplicate
in PK/UK)” when the length of the offending key was 127 characters or longer
fixed by D. Yemanov
~ ~ ~
(CORE-4761)
ON CONNECT triggers would
sometimes fail to execute
fixed by V. Khorsun
~ ~ ~
(CORE-4759)
A request synchronization error
could occur while building an expression index
fixed by V. Khorsun
~ ~ ~
(CORE-4754)
Bugcheck 167 (invalid SEND request)
could occur while working with a GTT from several attachments, using EXECUTE STATEMENT ... ON
EXTERNAL and different roles
fixed by V. Khorsun
~ ~ ~
(CORE-4752)
EXECUTE STATEMENT using BLOB parameters
could result in an “Invalid BLOB ID” error
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-4747)
The error “invalid BLOB ID”
could occur when retrieving MON$STATEMENTS.MON$SQL_TEXT using EXECUTE STATEMENT against an
EXTERNAL DATA SOURCE and the argument db_connect
was not specified
fixed by V. Khorsun
~ ~ ~
(CORE-4680)
Deadlock could occur during attachment
fixed by V. Khorsun
~ ~ ~
(CORE-4656)
The server could hang while chasing dead
record versions.
fixed by D. Starodubov
~ ~ ~
(CORE-4276)
CREATE TABLE would throw an error if a
column was being defined with the character set DOS775
fixed by A. dos Santos Fernandes
~ ~ ~
(CORE-214)
COUNT(DISTINCT ...) was too slow
fixed by D. Yemanov
~ ~ ~
(CORE-4982)
The server could crash during “select
from procedure” if an exception were thrown while backing out the current savepoint
fixed by D. Yemanov
~ ~ ~
(CORE-4785)
A bad op_execute
packet would kill the server
fixed by A. Peshkov
~ ~ ~
(CORE-4919)
On AIX and Solaris, all processes
on a Classic server would hang after the death of one process
fixed by A. Peshkov
~ ~ ~
(CORE-4869)
A segmentation fault could occur
when cleaning the metadata cache
fixed by A. Peshkov
~ ~ ~
(CORE-4788)
The Superclassic server could hang
when receiving a network packet
fixed by A. Peshkov
~ ~ ~
(CORE-4860)
Online validation on Windows would
fail if the dbname
argument contained forward slash ('/') and
a concurrent attachment existed that also used '/'
fixed by V. Khorsun
~ ~ ~
(CORE-4753)
Embedded server on Windows could hang due to
a synchronization problem involving artifact child processes that were not detectable by
Firebird
fixed by V. Khorsun
~ ~ ~
(CORE-4020)
The Control Panel applet
Firebird2Control.cpl
would crash in Windows 8
fixed by P. Reeves
~ ~ ~
Firebird Documentation Index → Firebird 2.5 Release Notes → Bugs Fixed → Firebird 2.5.5 Release |