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

Firebird 3.0 Release Candidate 2: Bug Fixes and Minor Improvements

Core Engine
Server Crashes
Database Encryption
API/Remote Interface
Utilities
Builds and Installers

The following tweaks and bug fixes were reported prior to v.3.0.0 release candidate 2:

Minor Improvements

(CORE-4996)     NEW: SECURITY2.FDB —> SECURITY3.FDB upgrade feature

Implemented by A. Peshkov

    ~ ~ ~     

(CORE-1538)     NEW: An option was added to the API function isc_database_info() to return the number of free pages in a database.

Implemented by V. Khorsun

    ~ ~ ~     

(CORE-5112)     IMPROVEMENT: The error messages for a malformed SQDLA were improved.

Implemented by D. Sibiryakov

    ~ ~ ~     

(CORE-5100)     IMPROVEMENT: Improved control over database crypt keys, see Encryption Tasks.

Implemented by A. Peshkov

    ~ ~ ~     

(CORE-5083)     IMPROVEMENT: A method was provided to set the correct offsets in user-implemented IMessageMetadata.

Implemented by A. Peshkov

    ~ ~ ~     

(CORE-5077)     IMPROVEMENT: In isql, SHOW DATABASE includes the encryption status of the database, as does gstat -h[eader].

Implemented by A. Peshkov

    ~ ~ ~     

(CORE-5063)     IMPROVEMENT: In isql, SHOW DATABASE includes the numbers of used and free pages in the database.

Implemented by V. Khorsun

    ~ ~ ~     

(CORE-5028)     IMPROVEMENT: The remote port number was added to the monitoring table MON$ATTACHMENTS.

Implemented by V. Khorsun

    ~ ~ ~     

(CORE-4978)     IMPROVEMENT: Validation and repair of lost data pages have been improved.

Implemented by R. Simakov, V. Khorsun

    ~ ~ ~     

(CORE-2493)     IMPROVEMENT: The IP address of the remote host is now appended to error messages in firebird.log for TCP connections.

Implemented by V. Khorsun

    ~ ~ ~     

Bugs

Core Engine

(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-5104)     SELECTs from an external data source would become slow.

fixed by V. Khorsun, A. Peshkov

    ~ ~ ~     

(CORE-5097)     COMPUTED BY expressions were not being converted to their data type inside the engine.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5093)     ALTER COLUMN was not changing the type of a computed column where it should.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5082)     The server was not validating the correctness of the user/password pair provided in the EXECUTE STATEMENT operation.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5078)     The "Invalid BLOB ID" error was being thrown unexpectedly after a large VARCHAR column was changed to text BLOB.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5075)     ON DISCONNECT trigger with EXECUTE STATEMENT was not working and would lead to a server crash when it was recreated.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5062)     

fixed by A. dos Santos FernandesFunction CHAR_TO_UUID on an indexed column would throw the error "expression evaluation not supported".

    ~ ~ ~     

(CORE-5060)     CREATE VIEW that selected from a system table would fail, despite all grants being available.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5056)     The write lock on the database file was being cleared when retrieving the database statistics via the Services API.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5049)     Byte-length for view columns was being calculated incorrectly.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5047)     mapUser() routine would establish a secondary attachment using the wrong provider.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5039)     Connecting to a service with an invalid service name would yield an incorrect error message.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5034)     A delay of at least 5 seconds could occur on disconnect if the disconnect followed closely on an Event Manager initialization.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5033)     The file fb_user_mapping could be left behind in the Firebird lock directory after a correct shutdown of all Firebird worker processes.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5032)     Connection to a database with its own security database was not possible in the absence of security3.fdb.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5026)     Firebird authentication would give up after failing to establish authentication via the first common plugin.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5020)     An ORDER BY clause on the key columns of a compound index could disable usage of other indices.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5018)     Non-indexed predicates might not have been applied immediately after retrieval when tables were being joined.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5017)     Interrupt of aux connection during TCP setup phase would cause a server exit due to an unhandled exception.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5014)     Interrupt of aux connection during TCP setup phase was producing unclear error messages in firebird.log.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4997)     Races would occur when two threads tried simultaneously to establish the first enbedded connection to the engine.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4991)     The Keyholder plug-in was being loaded on connection to a database but not on creating a database.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4980)     The REVOKE operator could modify the privileges granted to system tables at database creation time.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4969)     The SEC$USERS table became unavailable when an error occurred in any configured UserManager plug-in.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4964)     Real errors during connection to a security database were being hidden by the Srp user manager.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4885)     Retrieving the current user name when using Windows trusted authentication and an OS user name containing non-ASCII characters would cause an error.

fixed by A. Peshkov, D. Yemanov

    ~ ~ ~     

(CORE-4840)     Transactions with isc_tpb_autocommit could hang the server.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-2923)     Dependencies with views were exhibiting a problem.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Server Crashes

(CORE-5107)     SET AUTODDL OFF and sequence of CREATE + ALTER + DROP VIEW would lead to a server crash.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

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

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5016)     The server could crash during garbage collection when a DELETE is executed after adding a new referencing column.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5015)     The server could crash when an event was posted from an ON DISCONNECT trigger.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4982)     The server could crash during a select from a procedure if an exception was thrown while backing out the current savepoint.

fixed by D. Yemanov

    ~ ~ ~     

Database Encryption

(CORE-5105)     Deadlocks could occur when a database was initially encrypted.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5044)     Pages were being encrypted for each shadow separately.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5041)     A database could be corrupted after ALTER DATABASE ENCRYPT/DECRYPT was issued multiple times per database open time.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4999)     Trying to access a database with an invalid crypt key would cause a deadlock.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4990)     Databases were not being decrypted completely.

fixed by A. Peshkov

    ~ ~ ~     

API/Remote Interface

(CORE-5102)     fbclient.dll API calls were (wrongly) modifying the FPU control word.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5067)     New connections were being blocked as a consequence of sweeps of the security database taking too long.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5042)     The V.3 client could not create a database on a V.2.5 server.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5029)     A crash could occur in fbclient when a multi-threaded application was using the XNET protocol.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4998)     Neither client nor server could close the connection after failed authentication.

fixed by V. Khorsun

    ~ ~ ~     

Utilities

gbak

(CORE-5102)     Restore wass slow when the database contained many small tables with indices.

fixed by V. Khorsun

    ~ ~ ~     

gstat

(CORE-5088)     A segmentation fault could occur while gstat -h was closing.

fixed by A. Peshkov

    ~ ~ ~     

isql

(CORE-5092)     The EXTRACT command would lose the data types of COMPUTED BY columns.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5089)     Metadata extraction (isql -X): A "CREATE PROCEDURE/FUNCTION" statement would retain the TYPE OF reference to a table column that no longer existed, if the procedure or function had a parameter of that type declared at the time it was created.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5061)     Plan output was being unexpectedly truncated after a query was simplified by shortening it.

fixed by D. Yemanov

    ~ ~ ~     

Monitoring

(CORE-4708)     Content of MON$EXPLAINED_PLAN in MON$STATEMENTS was being truncated if it exceeded the 32KB limit.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4179)     The MON$ tables became unavailable when there was intensive disk-bound load.

fixed by D. Yemanov

    ~ ~ ~     

Builds and Installers

(CORE-5053)     (POSIX): changeServerMode.sh could mess with configuration.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5002)     (WINDOWS): The Windows installer exhibited some character set confusion (ANSI vs. UTF8) in its GUI for non-English environments.

fixed by P. Reeves

    ~ ~ ~     

(CORE-4910)     (WINDOWS): The Windows build would fail if a path to source files contained spaces.

fixed by D. Sibiryakov

    ~ ~ ~     

(CORE-4862)     (WINDOWS): ibase.h from the x64 package included a nonexistent file.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4842)     (POSIX): the installer script would fail in some Linux environments.

fixed by A. Peshkov, M. Masyk

    ~ ~ ~     

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