Download Firebird 2.5.8

Well-known databases for storing large amounts of data are of course the Oracle database, the DB2 database from IBM and SQL Server from Microsoft. Another database management system is Firebird, which originates from Inprise’s Interbase database. Inprise later became known as Borland Software and is now called Micro Focus. The history, as far as relevant to Firebird, is on this page to read. This relational database can be installed on a variety of operating systems, including Linux and Windows platforms, making it widely deployable. The developers have released version 2.5.8 with the following changes:

Improvements

• (CORE-5674) Common Table Expressions are now allowed to be left unused.
• (CORE-5640) Multiple simultaneous new connections to a database in Superclassic no longer cause a response bottleneck for one another.
• (CORE-5629) Output from gstat now includes the date and time of analysis.
• (CORE-5543) Restoring a pre ODS 11.1 database now correctly populates RDB$RELATION_TYPE field in the metadata.

Bug fixes

Core Engine

• (CORE-5685) It was sometimes not possible to cancel or kill the connection in which an external query was executing.
• (CORE-5684) Error “no current record for fetch operation” could be raised while deleting record from MON$ATTACHMENTS using ORDER BY clause.
• (CORE-5681) An access violation could occur when an external statement was executed and the local transaction was rolled back.
• (CORE-5675) isc_vax_integer() and isc_portable_integer() did not work properly with short negative numbers.
• (CORE-5655) isc_info_sql_relation_alias was reporting incorrect aliases for CTE or nested queries.
• (CORE-5650) Dropping a procedure on the Classic server could cause a segmentation fault.
• (CORE-5643) Message “Operating system call munmap failed. Error code 12” could appear in firebird.log under heavy load in Classic or Superclassic.
• (CORE-5641) A segmentation fault could occur when exiting classic server with a running sweep thread.
• (CORE-5624) An old bug was fixed, whereby backslashes in path strings for use on POSIX file systems were not always converted to forward slashes.
• (CORE-5591) The engine could hang during transaction start, soon after certain errors.
• (CORE-5528) Internal Firebird consistency check (limbo impossible (184), file: vio.cpp line: 2379)
• (CORE-5522) Engine could freeze up to two minutes and raise a deadlock error when updating RDB$INDICES if it contained back versions.
• (CORE-5521) A race condition could arise between event notification and event registration.
• (CORE-5415) Found and fixed an elusive bug in Firebird 2.5.7, as well as some older and newer versions, whereby an unexpected memory overwrite could cause the in-memory image of a random database page to be corrupted.
• (CORE-2731) Recursive EXECUTE STATEMENT was not working properly.
• (CORE-2502) Cyclic dependency errors in CTE, involving aliases.

API

• (CORE-5530) A client application using events could suffer an unpredictable access violation when the connection was broken.
• (CORE-3596) The client library could not connect to a non-ASCII host name.

Utilities – gbak

• (CORE-5579) A request synchronization error could occur in gbak during a restore.
• (CORE-5566) The server could crash while restoring from a backup if the shadow file already existed.