Firebird Documentation IndexFirebird 3.0.2 Release NotesBugs Fixed → Firebird 3.0 Second Alpha Release
Firebird Home Firebird Home Prev: Firebird 3.0 First Beta ReleaseFirebird Documentation IndexUp: Bugs FixedNext: Firebird 3.0 First Alpha Release

Firebird 3.0 Second Alpha Release

Core Engine
Server Crashes
API/Remote Interface
Security/User Management
Procedural Language
Data Definition Language
Data Manipulation Language
Utilities
International Language Support
Installation Issues

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

Core Engine

(CORE-4302)     Descending index could be very inefficient for some keys

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4289)     A NOT NULL field from a derived table could become NULL when referred to from outside the derived table

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4281)     TYPE OF arguments of stored functions could cause the server to hang if depending on a domain or column that had been changed

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4270)     A subquery involving a windowed function and a where <field> IN(select ...) condition could cause an error

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4265)     An unexpected lock conflict error could be raised while connecting to a heavily loaded database

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4262)     Context parsing errors could occur with derived tables and CASE functions

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4261)     JOIN result could be wrong when joined fields had been created via the row_number() function

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4258)     The boundary for the minimum value for BIGINT/DECIMAL(18) was wrong

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4251)     The Guardian service could write garbage after the end of a message in the Event Log

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4250)     Access violation could occur in Guardian at process shutdown

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4237)     Metadata being reported from system table queries for UDF return arguments was different to that returned in Firebird 2.5

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4234)     IF (subfunc()) would throw an error when subfunc returned a Boolean

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4229)     Bidirectional cursor was not being positioned by the first call of FETCH LAST

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4227)     A parser conflict was causing wrong evaluation of BETWEEN and Boolean expressions

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4216)     Memory leak with TRIGGER ON TRANSACTION COMMIT

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4211)     The embedded engine would hang for 5 seconds when closing, with errors about timeout in shutdown process and invalid mutex being written into firebird.log

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4201)     A computed field would return NULL inside a BEFORE INSERT trigger

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4198)     An incorrect “token unknown” error would occur when an SQL string ended with a hex number literal

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4177)     Some Boolean expressions were not being allowed

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4159)     Incorrect memory statistics were being reported

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4156)     RDB$GET_CONTEXT/RDB$SET_CONTEXT parameters were being described incorrectly as CHAR NOT NULL instead of VARCHAR NULLABLE

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-3689)     Bad performance and slow response were exhibited when many concurrent sorts were executed

fixed by D. Yemanov

    ~ ~ ~     

(CORE-3291)     With bugcheckabort=1 and sweep starting at gap ~21000, “Bugcheck 186 (record disappeared)” and 100% CPU load would occur

fixed by V. Khorsun

    ~ ~ ~     

(CORE-2165)     Unnecessary index reads could occur when using a strict inequality condition

fixed by V. Khorsun

    ~ ~ ~     

Server Crashes

(CORE-4293)     The server could crash on a SELECT with a long or complex list of compound AND/OR'd predicates

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4271)     Recreation of an errant package body could cause the engine to crash

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4268)     Disconnecting from a database could cause a server crash

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4267)     Sweeping a database could cause a server crash

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4225)     The server could crash when trace activity was attempted on a database having a database-level trigger

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4185)     Server crashes could occur, reporting “invalid lock id (NNNNN)

fixed by A. Peshkov

    ~ ~ ~     

API/Remote Interface

(CORE-4283)     Resource temporarily unavailable” errors could occur while events were being registered simultaneously

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4236)     Database shutdown was being reported as successfully completed before all active connections had actually been interrupted

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4178)     The new API was still returning obscure historical definition artifacts of data fields, instead of proper metadata properties that would make the interface actually usable

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4162)     Warnings were not being returned from calls to attachDatabase()

fixed by A. Peshkov

    ~ ~ ~     

Security/User Management

(CORE-4241)     Log-in could succeed with an empty password

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4200)     An uncommitted SELECT from the pseudo table sec$users would block new database connections

fixed by A. Peshkov

    ~ ~ ~     

Procedural Language

(CORE-4247)     Positioned DELETE (WHERE CURRENT OF <CURSOR>) could fail for tables with newly added fields

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4244)     Creating a procedure could be a problem if it involved adding text in DOS864 character set

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4184)     An error would be raised while executing an empty EXECUTE BLOCK with NOT NULL output parameter

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4160)     A parameterized exception would mishandle non-ASCII characters passed as the parameter

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4145)     Preparing an EXECUTE BLOCK that used domains was causing a memory leak

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Data Definition Language

(CORE-4214)     Global temporary tables were able to reference permanent relations, which they should not be able to do

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4212)     Dropping a foreign key on a Global temporary table would cause a server crash

fixed by V. Khorsun

    ~ ~ ~     

(CORE-4203)     Packaged routines with CHAR or VARCHAR parameters could not be created

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4180)     CREATE COLLATION was not verifying the base collation character set

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4173)     Setting a generator value twice in a single transaction would set it to zero

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4155)     External routines DDL in packages was wrongly reporting termination with semi-colon as an error

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Data Manipulation Language

(CORE-4269)     Wrong output would be produced when a field with the result of a windowed function was used in a query with a useless WHERE 0=0 and GROUP BY clause

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4255)     Parameterized queries using RDB$DB_KEY would not work

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4240)     Recursive query would return incorrect results if passage through more than one branch was requested

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4158)     LIKE with escape was not working

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Utilities

gfix

(CORE-4297)     gfix would crash when the size of the description of a limbo transaction was larger than 1 KB

fixed by V. Khorsun

    ~ ~ ~     

fbsvcmgr

(CORE-4298)     fbsvcmgr was not recognising sts_record_versions and other sts switches

fixed by A. Peshkov

    ~ ~ ~     

isql

(CORE-4259)     Bug in the isql command setlocale(LC_CTYPE, "") on Windows due to a reference to editline, which is not available on that platform

fixed by F. Schlottmann-Goedde

    ~ ~ ~     

(CORE-4205)     ISQL -x was failing to output the START WITH clause of generators/sequences

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-4149)     New permission types were not being displayed by isql

fixed by D. Yemanov

    ~ ~ ~     

(CORE-362)     It was impossible to enter certain characters in isql

fixed by F. Schlottmann-Goedde

    ~ ~ ~     

gbak

(CORE-4202)     Backup/restore from an older version to v.3.0 would fail with a BLR error

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4168)     A backup containing procedures or triggers that selected from external tables could not be restored with ExternalFileAccess = None

fixed by D. Yemanov

    ~ ~ ~     

(CORE-4164)     Owner name was missing for generators and exceptions restored from a backup

fixed by D. Yemanov

    ~ ~ ~     

nbackup

(CORE-2648)     nBackup's delta file was ignoring the Forced Writes setting of the database

fixed by V. Khorsun

    ~ ~ ~     

Database Monitoring (MON$)

(CORE-4235)     Deadlock could occur while accessing the monitoring tables under concurrent load

fixed by D. Yemanov & V. Khorsun

    ~ ~ ~     

(CORE-4176)     Monitoring tables were returning incomplete information in Classic and Superclassic configurations

fixed by D. Yemanov

    ~ ~ ~     

Trace

(CORE-4219)     Regular expressions with double-slash would fail in trace

fixed by A. Peshkov

    ~ ~ ~     

(CORE-4163)     Configuration file fbtrace.conf contained syntax errors

fixed by A. Peshkov

    ~ ~ ~     

International Language Support

Installation Issues

(CORE-4153)     Attempting to use Legacy_Auth directly after install would not work without restarting the service

fixed by P. Reeves

    ~ ~ ~     

Prev: Firebird 3.0 First Beta ReleaseFirebird Documentation IndexUp: Bugs FixedNext: Firebird 3.0 First Alpha Release
Firebird Documentation IndexFirebird 3.0.2 Release NotesBugs Fixed → Firebird 3.0 Second Alpha Release