FirebirdSQL logo

Compatibility with Older Versions

Known incompatibilities are detailed in the Compatibility Issues chapter.

Sub-release V.5.0.1

Bugs reported and fixed prior to the version 5.0.1 release are listed HERE.

V.5.0.1 Improvements

#8181 — Ensure the standalone CS listener on Linux uses the SO_REUSEADDR socket option

Implemented by Dmitry Yemanov


#8165 — Added shutdown handler for Classic Server

Implemented by Alexander Peshkov, Alexander


#8104 — More efficient evaluation of expressions like RDB$DB_KEY <= ? after mass delete

Implemented by Vlad Khorsun


#8066 — Make protocol schemes case-insensitive

Implemented by Vlad Khorsun


#8061 — Unnest IN/ANY/EXISTS sub-queries and optimize them using semi-join algorithm

See also the configuration parameter SubQueryConversion.

Implemented by Dmitry Yemanov


#8042 — Improve conflict resolution on replica when table has both primary and unique keys

Implemented by Vlad Khorsun


#8030 — Better cardinality estimation when empty data pages exist

Implemented by Vlad Khorsun


#8010 — Remove gfix -cache option

Implemented by Vlad Khorsun


#7978 — Update Windows distributions with zlib version 1.3.1

Implemented by Vlad Khorsun


#7928 —  Make TempCacheLimit setting to be per-database (not per-attachment) for SuperClassic

Implemented by Vlad Khorsun


Bug Reporting

Bugs fixed in this release are listed and described in the chapter entitled Bugs Fixed.

  • If you think you have discovered a new bug in this release, please make a point of reading the instructions for bug reporting in the article How to Report Bugs Effectively, at the Firebird Project website.

  • If you think a bug fix has not worked, or has caused a regression, please locate the original bug report in the Tracker, reopen it if necessary, and follow the instructions below.

Follow these guidelines as you attempt to analyse your bug:

  1. Write detailed bug reports, supplying the exact build number of your Firebird kit.Also provide details of the OS platform.

  2. Include reproducible test data in your report and post it to our Tracker.