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

Bugs Fixed

Table of Contents

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.5 Release: Bug Fixes

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

Core Engine

(CORE-6203)     "Error reading data from the connection" could be raised sometimes when using a non-default authentication plugin.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6197)     The client library could leak memory when resolving the remote host name.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6182)     Firebird's internal timer could incorrectly reset the other existing timer entries.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6171)     Error "No current record for fetch operation" could be raised for queries containing an aggregated sub-select.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6163)     Generator pages were not encrypted.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6150)     Bugcheck could be raised when some PK\UK\FK constraint checks a record already marked as damaged.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6144)     Inconsistent behaviour of the NEW context variable was observed in AFTER UPDATE OR DELETE triggers.

fixed by I. Eremin

    ~ ~ ~     

(CORE-6143)     Error "Multiple maps found for ..." was raised in not appropriate case.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6138)     Inconsistent behavior was observed regarding visibility of the master record while inserting the detail record.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6134)     Different error messages ("Your user name and password are not defined" vs "Missing security context") could be reported for a failed login depending on whether the Win_SSPI plugin is present in the configuration.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6108)     Error "Datatypes are not comparable in expression" could be raised for a COALESCE function used inside an expression.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6097)     Connection could not see itself in MON$ATTACHMENTS when Windows domain/username (using Win_SSPI authentication) is exactly 31 bytes long.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6090)     BLOB fields could be suddenly set to NULLs during UPDATE after a table format change.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6089)     BLOBs were unnecessarily copied during UPDATE after a table format change.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-6087)     CAST function used inside a union could be ignored.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6078)     CREATE OR ALTER series of statements were ignoring the existing permissions.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6067)     The client library could leak memory if DSQL cursors are closed after the transaction commit.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6063)     Firebird server could return the 'op_accept' packet instead of the expected 'op_accept_data' one.

fixed by D. Kovalenko

    ~ ~ ~     

(CORE-6050)     The client library was attempting to open files not existent on the client host when connecting to a remove v2.5 server.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6043)     Global temporary tables created with the ON COMMIT DELETE ROWS clause were not releasing their used space in the temporary file(s) at COMMIT RETAINING or ROLLBACK RETAINING.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-6038)     Srp user manager could sporadically create user accounts that cannot pass the authentication.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5995)     The "creator" user name was empty in user trace sessions.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5993)     Error message was missing inside firebird.log after failure to create the audit log file.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5991)     Trace could not work correctly with quoted file names in the trace configurations.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5986)     Condition NULL IS [NOT] {FALSE | TRUE} was evaluated incorrectly (NULL was returned instead of the expected FALSE/TRUE).

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5985)     ROLE option was ignored when specified for a remote EXECUTE STATEMENT command.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5982)     Error "no permission for SELECT access" could be raised when a BLOB is used as input or output parameter of a stored procedure.

fixed by D. Starodubov

    ~ ~ ~     

(CORE-5966)     Slow performance could be noticed when executing SQL scripts as non-SYSDBA user.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5965)     v3 optimizer could choose a less efficient plan than the v2.5 optimizer.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5949)     Bugcheck could happen when a read-only database with non-zero linger is converted into a read-write mode.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5935)     Bugcheck 165 ("cannot find tip page") could happen under load in Classic and SuperClassic.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5926)     CREATE MAPPING with non-ASCII user name could lead to the "Malformed string" error message.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5918)     Memory statistics ('used' / 'mapped' counters) was not always accurate.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5907)     Trace session could not be started if the 'database' section contains a pattern including curvy brackets.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5888)     Firebird server on Android had problems with NUMERIC values (scale was not reported properly).

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5823)     Error "no permission for SELECT access" was raised when selecting a BLOB field from a stored procedure.

fixed by D. Starodubov

    ~ ~ ~     

(CORE-5795)     ORDER BY clause on compound index could prevent from using other available indices.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5784)     Lock folder inizialization was not multi-process safe.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5639)     Mapping created for the Win_SSPI plugin did not cause the Windows user group to be converted to a Firebird role.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5395)     Error "Invalid data type for negation" was raised for a query containing a negated parameter.

fixed by A. dos Santos Fernandes, D. Yemanov

    ~ ~ ~     

(CORE-5074)     Charset ID of the array element could be lost (zero was always reported) when preparing a query selecting from that array field.

fixed by D. Kovalenko

    ~ ~ ~     

(CORE-5070)     Compound index could not be used for filtering in some ORDER/GROUP BY queries.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-3925)     Bugcheck could be raised after attempting to create a self-referencial FK that violates the existing data.

fixed by V. Khorsun

    ~ ~ ~     

Server Crashes/Hang-ups

(CORE-6086)     Server could crash while creating some complex stored procedure (containing multiple CTEs).

fixed by V. Khorsun, D. Yemanov

    ~ ~ ~     

(CORE-6068)     Server could hang while compiling a large package body containing a syntax error.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-6027)     Server could hang at the incoming attachment if it happened immediately after the trace session has been stopped.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6015)     Server crash could happen while using the computed index based on a complex expression.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5980)     Firebird could crash during concurrent operations with expression indices.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5972)     External engine trigger was causing the server to crash if the underlying table has computed field(s).

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5950)     Server could deadlock when some user attaches a bugchecked database.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5943)     The server could crash preparing a query having DISTINCT or ORDER BY together with a non-field expression in the select list.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5936)     The Firebird server could crash at the end of a gbak backup.

fixed by V. Khorsun

    ~ ~ ~     

Builds

(CORE-6007)     Firebird would not build on MacOS with the fresh toolchain installed, compilation failed while building the 'editline' library.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5989)     Linking the binaries could fail due to missing 'libiconv_open' reference if the libiconv library is installed.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5934)     gpre_boot was failing to link using CMake, reporting undefined reference 'dladdr' and 'dlerror'.

fixed by A. Peshkov

    ~ ~ ~     

API/Remote Interface

(CORE-6142)     Error "connection lost to database" could be raised when application creates multiple local attachments (using the XNET protocol) simultaneously.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5927)     Connection could remain not encrypted using some non-standard authentication plugins even if a correct key was provided.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5902)     Events processing was not working between Windows and MacOS hosts.

fixed by A. dos Santos Fernandes, V. Khorsun

    ~ ~ ~     

POSIX Only

(CORE-6031)     The first connection to any database was causing a small memory leak related to the 'binreloc' library initialization.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6026)     Incorrect alignment was used for the BIGINT data type transferred from/to UDR libraries in 32-bit Linux builds.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5955)     The binreloc library could fail to initialize properly with ld versions 2.31 and above, causing the Firebird binaries to wrongly detect its root directory.

fixed by R. Simakov

    ~ ~ ~     

MacOS Only

(CORE-6122)     An attempt to call the properly declared UDF was raising the "module name or entrypoint could not be found" error on MacOS Mojave (10.14.3).

fixed by P. Beach

    ~ ~ ~     

Windows Only

(CORE-5959)     Firebird could return incorrect (outdated) current time/timestamp after the time zone was changed at the operating system level.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-3900)     VC runtime installer could reboot the system before the Firebird installation process finishes.

fixed by B. Walker, P. Reeves

    ~ ~ ~     

Utilities

gbak

(CORE-6028)     User-defined triggers declared for system tables were included into backups, and it is impossible to alter/drop them due to system tables protection in Firebird 3. Starting with V3.0.5, gbak skips such triggers during both backup and restore operations.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-6000)     gbak was reporting the authentication error "Your user name and password are not defined" when the "-fe(tch_password)" command switch is specified and gbak was running as a service.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5118)     Indices on computed fields were broken after a restore, with all keys being set to NULL.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-2440)     Restoring a database with a computed index on a computed field was providing the wrong index and wrong query results.

fixed by D. Yemanov

    ~ ~ ~     

gpre

(CORE-6104)     Incorrect error "invalid request handle" was raised by the gpre-generated code when an embedded user does not have proper permissions for the table.

fixed by D. Yemanov

    ~ ~ ~     

isql

(CORE-6040)     Metadata script extracted using isql -x was invalid if some table contains a COMPUTED BY column.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

nBackup

fbsvcmgr

(CORE-6141)     fbsvcmgr action_repair rpr_list_limbo_trans was not showing the expected list of 'in limbo' transactions.

fixed by A. Peshkov

    ~ ~ ~     

fbtracemgr

(CORE-6045)     Segmentation fault could happen in fbtracemgr while closing it using the Ctrl-C keystroke.

fixed by A. Peshkov

    ~ ~ ~     

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