Firebird Documentation IndexFirebird 3.0.6 Release Notes → Bugs Fixed
Firebird Home Firebird Home Prev: Remote Client RecognitionFirebird Documentation IndexUp: Firebird 3.0.6 Release NotesNext: Firebird 3.0.5 Release: Bug Fixes

Chapter 13: Bugs Fixed

Table of Contents

Firebird 3.0.6 Release: Bug Fixes
Firebird 3.0.5 Release: Bug Fixes
Firebird 3.0.4 Release: Bug Fixes
Firebird 3.0.3 Release: Bug Fixes
Firebird 3.0.2 Release: Bug Fixes
Firebird 3.0.1 Release: Bug Fixes
Firebird 3.0.0 Release: Bug Fixes
Firebird 3.0 Release Candidate 2: Bug Fixes and Minor Improvements
Firebird 3.0 Release Candidate 1: Bug Fixes and Minor Improvements
Firebird 3.0 Second Beta Release: Bug Fixes
Firebird 3.0 Second Beta Release: Improvements
Firebird 3.0 First Beta Release
Firebird 3.0 Second Alpha Release
Firebird 3.0 First Alpha Release

Firebird 3.0.6 Release: Bug Fixes

The following bug fixes were reported prior to the v.3.0.6 official release:

Core Engine

(CORE-6343)     Rolled back transaction could produce unexpected results leading to duplicate values in the primary key.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6331)     Memory leak was possible when executing some statements and expressions.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6323)     File-system ID could be duplicated among databases located on different volumes.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6314)     Assigning RDB$DB_KEY to a multi-byte CHAR/VARCHAR variable/parameter did not enforce the target limit.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6310)     Varchar length limit was not enforced when assigning a string with trailing spaces in multi-byte character sets.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6296)     Many connections could result in poor performance.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6290)     Hex number used at the end of statement could read invalid memory and produce wrong values or exceptions.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6280)     MERGE statement could lose parameters in the "WHEN [NOT] MATCHED" clause that will never be matched. This could also cause server crashes in some situations.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6266)     Deleting records from MON$ATTACHMENTS using the ORDER BY clause didn't close the corresponding attachments.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6252)     UNIQUE CONSTRAINT violation could be possible.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6250)     Signature mismatch error could be raised when creating package body on identical packaged procedure header.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6246)     Output parameters could be wrongly described if there are too many number of columns in the result set.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6230)     It was impossible to connect to a database if security.db reference was removed from databases.conf.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6221)     Incorrect implementation of allocFunc() for zlib1: memory leak was possible.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6110)     64-bit transaction IDs were not stored properly inside the status vector.

fixed by I. Eremin

    ~ ~ ~     

(CORE-5862)     RDB$CHARACTER_LENGTH in RDB$FIELDS was not being populated when the column was a computed VARCHAR without an explicit type.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Server Crashes/Hang-ups

(CORE-6345)     Server could crash on overflow of numeric division result.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6317)     Server could crash executing long GRANT statements.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6254)     Server could crash when using SET TRANSACTION and ON TRANSACTION START trigger uses EXECUTE STATEMENT against current transaction.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6253)     Locked fb_lock file could cause a server crash.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6251)     Server would crash when built-in function LEFT or RIGHT is missing its 2nd argument.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6231)     Server would crash during shutdown of XNET connection to a local database when events have been registered.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6224)     Server could crash due to double destruction of the rem_port object.

fixed by D. Kovalenko, A. Peshkov

    ~ ~ ~     

(CORE-6217)     Dangerous (possibly leading to a crash) work with pointer: delete ptr; ptr=new ;.

fixed by D. Kovalenko, A. Peshkov

    ~ ~ ~     

(CORE-5972)     External engine trigger would crash the server if the table has computed fields.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Builds

(CORE-6295)     Distributed header files were incomplete (missing some type declarations).

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6189)     Building the bundled libtommath could fail.

fixed by A. Peshkov

    ~ ~ ~     

API/Remote Interface

(CORE-6283)     Result of isNullable() in message metadata, returned by metadata builder, did not match datatype set by setType() in metadata builder.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6227)     isc_info_svc_user_dbpath was always returning an alias of the main security database.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6212)     Authentication plugin on the server could read garbage data from the client instead of the empty packet.

fixed by A. Peshkov

    ~ ~ ~     

POSIX Only

(CORE-6269)     Server could ignore KeepAlive settings (server connection/process is not killed when its client endpoint is lost).

fixed by A. Peshkov

    ~ ~ ~     

Utilities

gbak

(CORE-6329)     GBAK with service_mgr and WinSSPI authentication could raise an error in clumplet API.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6265)     Existing mapping rules were removed by the backup/restore cycle.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6264)     GBAK with PIPE to stdout: invalid content in the 'service_mgr' mode.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6233)     Wrong dependencies of stored function on view were created after backup/restore.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6208)     CREATE DATABASE permission would disappear from security.db after the backup/restore cycle.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6130)     Creating backup to STDOUT using the service manager was broken.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-2251)     GBAK doesn't return the error code in some cases.

fixed by A. Peshkov

    ~ ~ ~     

gfix

(CORE-5364)     gfix -online normal did not raise an error when there was another SYSDBA-owned session open.

fixed by A. Peshkov

    ~ ~ ~     

isql

(CORE-6260)     Warnings were not always displayed in ISQL.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6116)     Metadata script extracted with ISQL from a database restored from a v2.5 backup was invalid if some table has COMPUTED BY fields.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

nBackup

(CORE-6319)     NBACKUP called via the Services API was locking the database file after error.

fixed by V. Khorsun

    ~ ~ ~     

fbsvcmgr

(CORE-6309)     fbsvcmgr could not decode information buffer returned by GFIX list limbo service.

fixed by A. Peshkov

    ~ ~ ~     

Prev: Remote Client RecognitionFirebird Documentation IndexUp: Firebird 3.0.6 Release NotesNext: Firebird 3.0.5 Release: Bug Fixes
Firebird Documentation IndexFirebird 3.0.6 Release Notes → Bugs Fixed