Firebird Documentation IndexFirebird 2.5 Release NotesBugs Fixed → Firebird 2.5.6 Release
Firebird Home Firebird Home Prev: Bugs FixedFirebird Documentation IndexUp: Bugs FixedNext: Firebird 2.5.5 Release

Firebird 2.5.6 Release

Core Engine
Server Crashes
Utilities
Windows-Specific

The following improvements and bug fixes were reported as fixed prior to the v.2.5.6 release:

Core Engine

(CORE-5216)     IMPROVEMENT: Run-time errors raised inside EXECUTE BLOCK now provide the location context (line/column numbers).

implemented by D. Yemanov

    ~ ~ ~     

(CORE-5275)     An expression index could become inconsistent if CREATE INDEX was interrupted after b-tree creation but before committing.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5241)     Affected rows were not being counted for some update operations with views.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5226)     The result set returned could be missing some rows when the query's ORDER plan navigated on a descending index.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5161)     It was possible to create a unique index on data that were not unique.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5157)     The server could go into an infinite loop when data were sent from a client to the service in small packets.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5122)     An expression index that was created in one character set and used in another character set could be ignored by the optimizer.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5110)     A false primary or foreign key violation could be reported when an attachment used the isc_dpb_no_garbage_collect flag.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5078)     Invalid BLOB ID” error, apparently subsequent to changing a large VARCHAR column to a text BLOB.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5062)     Using CHAR_TO_UUID on a column with an index would throw the error “Expression evaluation not supported. Human readable UUID argument for CHAR_TO_UUID must be of exact length 36”.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4870)     The number of affected rows was reported incorrectly for an update against a view created WITH CHECK OPTION.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4645)     Source of the error “Bugcheck 165 (cannot find TIP page)” was identified and fixed.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-1746)     It was possible to create an expression index while inserts into the table were in progress.

fixed by V. Khorsun

    ~ ~ ~     

Server Crashes

(CORE-5240)     A crash could occur while restoring a database with large page cache.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5117)     Firebird embedded could crash on unload if it was used to make a client connection to a full server.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5087)     Database shutdown could cause a server crash if multiple attachments were running EXECUTE STATEMENT.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5068)     REGRESSION: when gbak was run via the services manager with an invalid parameter, it would crash the server.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4983)     The server could crash during execution of an unprepared statement.

fixed by D. Yemanov

    ~ ~ ~     

Utilities

gbak

(CORE-5201)     IMPROVEMENT: gbak now returns a non-zero result code if restore fails on activating and creating a deferred user index.

fixed by A. Peshkov

    ~ ~ ~     

gfix

(CORE-5295)     Validation could read after the end-of-file when handling a multi-file database.

fixed by V. Khorsun

    ~ ~ ~     

isql

(CORE-5218)     Explicitly defined names for NOT NULL constraints were not being exported into the script produced by isql -[e]x[tract].

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5217)     isql -[e]x[tract] could crash while exporting an exception with message text length > 127 bytes.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4817)     isql was not showing the number of affected rows for MERGE ... WHEN MATCHING in cases where the number was known to be greater than zero.

fixed by C. Valderrama

    ~ ~ ~     

Windows-Specific

(CORE-5067)     Some issues with caching the security database could cause new connections to be blocked on Classic on Windows.

fixed by V. Khorsun

    ~ ~ ~     

Prev: Bugs FixedFirebird Documentation IndexUp: Bugs FixedNext: Firebird 2.5.5 Release
Firebird Documentation IndexFirebird 2.5 Release NotesBugs Fixed → Firebird 2.5.6 Release