Bugs
Error: database file appears corrupted after restore from backup
GitHub Issue: 7942 Affected versions: 5.0.0 Fixed for: 5.0.1, 6.0 Alpha 1
The problem is related to paraller index creation on Classic. Superserver is not affected.
"Too many temporary blobs" with blob_append when select a stored procedue using rows-clause
GitHub Issue: 8056 Affected versions: 4.0.4, 5.0.0 Fixed for: 4.0.5, 5.0.1, 6.0 Alpha 1
SIMILAR TO with constant pattern using ‘|’, ‘*’, ‘?’ or ‘{0,N}’ doesn't work as expected
GitHub Issue: 8078 Affected versions: 5.0.0 Fixed for: 5.0.1, 6.0 Alpha 1
Regression caused by wrong optimization implemented in 6873.
Bugcheck 183 (wrong record length) could happen on replica database after UK violation on insert
GitHub Issue: 8040 Affected versions: 4.0.4, 5.0.0 Fixed for: 4.0.5, 5.0.1, 6.0 Alpha 1
The conditions:
replica database contains a table with Primary Key and at least one Unique Key
the record is being inserted and violates UK (not PK!)
the correct error is put into replication.log:
ERROR: attempt to store duplicate value (visible to active transactions) in unique index <UK name> Problematic key value is (...)
after replication paused and resumed the same segment is applied again bugcheck happens: ERROR: internal Firebird consistency check (wrong record length (183), file: vio.cpp line: 1450)
Engine could crash when executing some trigger(s) while another attachment modifies them
GitHub Issue: 8079 Affected versions: 3.0.11, 4.0.4, 5.0.0 Fixed for: 3.0.12, 4.0.5, 5.0.1, 6.0 Alpha 1
AV when writting into internal trace log
GitHub Issue: 8083 Affected versions: 4.0.4, 5.0.0 Fixed for: 4.0.5, 5.0.1, 6.0 Alpha 1
Memory leak when executing a lot of different queries and StatementTimeout > 0
GitHub Issue: 8085 Affected versions: 4.0.4, 5.0.0 Fixed for: 4.0.5, 5.0.1, 6.0 Alpha 1
Partial index uniqueness violation
GitHub Issue: 8084 Affected versions: 5.0.0 Fixed for: 5.0.1, 6.0 Alpha 1
If the filtering field of a partial index is not included in the index key, then its uniqueness can be easily violated by updating the filtering field. This breaks backup/restore and index rebuilding.
AV when preparing a query with IN list that contains both literals and sub-query
GitHub Issue: 8087 Affected versions: 5.0.0 Fixed for: 5.0.1, 6.0 Alpha 1
Test case:
SELECT * FROM RDB$RELATIONS R WHERE R.RDB$RELATION_ID IN (1, (SELECT D.RDB$RELATION_ID FROM RDB$DATABASE D))
AV when attaching database while low of free memory
GitHub Issue: 8089 Affected versions: 3.0.11, 4.0.4, 5.0.0 Fixed for: 3.0.12, 4.0.5, 5.0.1, 6.0 Alpha 1
New features/improvements
Create if not exists
GitHub Issue: 8062 Apply to: 6.0 Alpha 1
Latest snapshot builds includes "drop if exists" support (at least for tables). Both "drop if exists" and "create if not exists" has been discussed in several other places including #4203 Since half of the job seems to be implemented, I would very much like to have the other half for v6.0.