The months that have passed since the initial release have seen numerous Tracker issues tackled to address things that have been reported broken, bent, or compromised in v.2.5. As well as a long list of bugfixes, a few minor improvements have been made.
Firebirdの2.5の主な目標は、低レベルの同期と一般的にスレッドの安全性を取り込み、ほぼ完全に共通Superサーバー、クラシック、および組み込みモデルにされ、新しいスレッドアーキテクチャの基礎を確立することだった。ユーザ管理とは、SQL CREATE /変更/ DROP USERをステートメントを介してアクセス可能なALTER VIEWを作成またはALTER VIEWのための構文が実装されています。 PSQLの改善は、自律型トランザクションの導入と能力をクエリEXECUTEステートメントを介して別のデータベースに含まれています。
Major bugfixes, Major feature enhancements, Stable
The primary goal for Firebird 2.5 was to establish the basics for a new threading architecture that is almost entirely common to the Superserver, Classic, and Embedded models, taking in lower level synchronization and thread safety generally. User management is accessible through SQL CREATE/ALTER/DROP USER statements, and syntaxes for ALTER VIEW and CREATE OR ALTER VIEW are implemented. PSQL improvements include the introduction of autonomous transactions and the ability to query another database via EXECUTE STATEMENT.
This release fixes various bugs. The server could stop responding to a particular client attachment under some conditions. There would be a small time window during which the remote server would ignore the incoming operation request it had just received and, thereby, seem to block the client application. The listener thread would remain operational, but the client would be synchronously waiting for the reply packet that would not come.