Firebird 3.0.0 (64-bit)

What's new in this version:

- The primary goals for Firebird 3.0 were to unify the server architecture and to improve support for SMP and multiple-core hardware platforms. Parallel objectives were to improve threading of engine processes and the options for sharing page cache across thread and connection boundaries.
- Alongside these aims came new strategies to improve performance, query optimization, monitoring and scalability and to address the demand for more security options. A number of popular features were introduced into the SQL language, including the long-awaited support for the Boolean data type and the associated logical predications.

BUGS FIXED:

Core Engine:
- An assertion would occur in the cloop dispatcher when trying to save exception information in the status interface.
- Failure to find a record on re-fetch would produce inconsistent effects on subsequent statement execution.
- Unique key violation on a BOOLEAN column was returning an erroneous message.
- HAVING COUNT(*) NOT IN ( ) would erroneously exclude a record from the outer result set. ( represents a result set without nulls)
- It was possible to create a unique index on non-unique data.
- Regression: the engine could throw transliteration errors when running from a non-ASCII system path.
- The server could go into an infinite loop when data was being sent from a client to the server in small packets.
- Regression: LEFT JOIN was incorrectly pushing COALESCE into the inner stream, causing wrong results.
- CREATE TRIGGER was failing with the error "Ambiguous field name between table B and table A".
- Join order was sub-optimal if one table had a selective predicate and MIN was calculated for the other one.
- Deadlock could occur when a database was being encrypted or decrypted under high parallel load.
- ALTER SEQUENCE RESTART WITH was failing to change the initial value.
- 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.
- 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.
- 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.

Server Crashes:
- Regression: The server would crash when aggregate functions were used together with the NOT IN predicate.

Utilities:
- gbak: gbak restore could fail when there was some SQL function accessing a table while the switch -O(NE_AT_A_TIME) was in use.
- gfix: An attempt to set the number of page buffers to a non-supported value would return the wrong error message.
- isql: An invalid COMPUTED BY definition was being generated by the 'extract metadata' operation.
- Monitoring: Database-level statistics (MON$STAT_GROUP = 0) could contain multiple rows under concurrent load.
- User Management: The codes of operation for user management plug-ins were missing from the public API.
- User Management: 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.
- User Management: [CREATE OR] ALTER USER statement would fail if the PASSWORD parameter was present and was not specified immediately after the USER parameter.

Builds:
- The build would fail if HAVE_MMAP was not defined.
- Root rights were unnecessarily required to build a Linux package.
- The samples of dbcrypt-related plug-ins contained references to internal files.