If there were statistics on corrupted Firebird databases, I believe more than 80% of them would have something in common: they were running with forced-writes off.
Since Firebird 2.1 forced-writes also work in linux. With that in mind I put together a comparison between the two modes.
Disabled metadata cache mode performance was increased in 2.5 times.
Metadata schemes were updated. Among them in schemes TABLE_INFO and TABLES classification of external (EXTERNAL TABLE) and temporary tables (GLOBAL TEMPORARY PRESERVE/DELETE) was added starting from Firebird 2.1 and Interbase 7.5.
Correct processing of active transactions in the connection pool.
New build IBProvider v1.9.9.2547 and IBProvider v2.6.3.2547
BLOB-columns metadata description bug was fixed.
Correct processing of active transactions in the connection pool.
Google led me to a comparison sheet about PostgreSQL and Firebird by AMSoftwareDesign, as it looks a bit outdated I decided to add some infos about the latest Firebird release, see it in action
After a long struggle on Devshed forums I decided to try on my own, after all I know Firebird and don’t see why it and ColdFusion can’t play nice together … infact they did, and easily.
Firebird 2.1 added the long-awaited monitoring tables. By querying special system tables starting with MON$, you get a snapshot of the current activities in your database like who is connected to your database, which transactions and statements are running and so on. You even can cancel a running query by executing a DELETE statement on MON$STATEMENTS. Firebird 2.5 will also allow you to cancel an entire attachment via a DELETE on MON$ATTACHMENTS.
The winner of the “Darwin Race of Languages” competition is Werewolf, who submited a nive GUI frontend for gbak (Windows and Linux), made in Delphi/Kylix. You can check more information and download it here.