Firebird Documentation IndexFirebird 3.0.2 Release NotesBugs Fixed → Firebird 3.0.0 Release: Bug Fixes
Firebird Home Firebird Home Prev: Firebird 3.0.1 Release: Bug FixesFirebird Documentation IndexUp: Bugs FixedNext: Firebird 3.0 Release Candidate 2: Bug Fixes and Minor Improvements

Firebird 3.0.0 Release: Bug Fixes

Core Engine
Server Crashes
Utilities
Builds

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

Core Engine

(CORE-5184)     An assertion would occur in the cloop dispatcher when trying to save exception information in the status interface.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5182)     Failure to find a record on re-fetch would produce inconsistent effects on subsequent statement execution.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5166)     Unique key violation on a BOOLEAN column was returning an erroneous message.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5165)     HAVING COUNT(*) NOT IN ( <Q> ) would erroneously exclude a record from the outer result set. (<Q> represents a result set without nulls)

fixed by A. dos Santos Fernandes

    ~ ~ ~     

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

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5159)     Regression: the engine could throw transliteration errors when running from a non-ASCII system path.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

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

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5149)     Regression: LEFT JOIN was incorrectly pushing COALESCE into the inner stream, causing wrong results.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5147)     CREATE TRIGGER was failing with the error "Ambiguous field name between table B and table A".

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5146)     Join order was sub-optimal if one table had a selective predicate and MIN was calculated for the other one.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5144)     Deadlock could occur when a database was being encrypted or decrypted under high parallel load.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5133)     ALTER SEQUENCE RESTART WITH was failing to change the initial value.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5130)     Minor regression: wrong error message was being returned on an attempt to compile a view with both a subquery and the WITH CHECK OPTION clause in its definition—an illegal combination.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5122)     The optimizer could avoid using an expression index if the query was running in a different connection character set to the one that was in effect when the index was created.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4645)     Internal Firebird consistency check (cannot find tip page (165), file: tra.cpp line: 2375) would occur if too many transactions were created for one connection to a read-only database. This was a very old bug, dating back to InterBase 6.

fixed by V. Khorsun

    ~ ~ ~     

Server Crashes

(CORE-5153)     Regression: The server would crash when aggregate functions were used together with the NOT IN predicate.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Utilities

gbak

(CORE-5143)     gbak restore could fail when there was some SQL function accessing a table while the switch -O(NE_AT_A_TIME) was in use.

fixed by D. Yemanov

    ~ ~ ~     

gfix

(CORE-5140)     An attempt to set the number of page buffers to a non-supported value would return the wrong error message.

fixed by V. Khorsun

    ~ ~ ~     

isql

(CORE-5194)     An invalid COMPUTED BY definition was being generated by the 'extract metadata' operation.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Monitoring

(CORE-5179)     Database-level statistics (MON$STAT_GROUP = 0) could contain multiple rows under concurrent load.

fixed by D. Yemanov

    ~ ~ ~     

User Management

(CORE-5189)     The codes of operation for user management plug-ins were missing from the public API.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5162)     Users with the same name can co-exist in the security database if they are created by different plug-ins. However, tags or attributes for a user created using one plug-in were being displayed in the SEC$ virtual tables for the same-name user created by the other plug-in.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5155)     [CREATE OR] ALTER USER statement would fail if the PASSWORD parameter was present and was not specified immediately after the USER parameter.

fixed by A. Peshkov

    ~ ~ ~     

Builds

(CORE-5181)     The build would fail if HAVE_MMAP was not defined.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5180)     Root rights were unnecessarily required to build a Linux package.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5134)     The samples of dbcrypt-related plug-ins contained references to internal files.

fixed by A. Peshkov

    ~ ~ ~     

Prev: Firebird 3.0.1 Release: Bug FixesFirebird Documentation IndexUp: Bugs FixedNext: Firebird 3.0 Release Candidate 2: Bug Fixes and Minor Improvements
Firebird Documentation IndexFirebird 3.0.2 Release NotesBugs Fixed → Firebird 3.0.0 Release: Bug Fixes