Firebird Documentation IndexFirebird 2.5 Release NotesCompatibility Issues → API Changes
Firebird Home Firebird Home Prev: UtilitiesFirebird Documentation IndexUp: Compatibility IssuesNext: Security Hardening

API Changes

Rejection of Inconsistent TPB Options
Addition of SQL_NULL Constant

Notice the following changes to the application programming interface (API) that is implemented in the client libraries.

Rejection of Inconsistent TPB Options

The API functions isc_start_transaction() and isc_start_multiple() will now reject combinations of transaction parameter buffer (TPB) items that do not “belong together”.

For example, a non-zero wait timeout is inconsistent with the no wait option; and no record version is inconsistent with any transaction isolation mode other than ReadCommitted. Now, instead of making some arbitrary (and possibly incorrect) assumption about the inherent ambiguities, the engine will reject such combinations as invalid.

For more information, see the topic Transaction Diagnostics in the chapter Changes in the Firebird Engine.

Addition of SQL_NULL Constant

New SQL_NULL constant was introduced to enable the predication OR ? IS NULL to be recognised and processed with the expected outcome and without engendering the “Data type unknown” exception. This affects how the XSQLVAR structures are populated for such queries. For information, refer to the topic SOME_COL = ? OR ? IS NULL Predication in the DML chapter.

Prev: UtilitiesFirebird Documentation IndexUp: Compatibility IssuesNext: Security Hardening
Firebird Documentation IndexFirebird 2.5 Release NotesCompatibility Issues → API Changes