Firebird Documentation IndexFirebird 2.5 Release NotesConfiguration Parameter Additions and Changes → OldSetClauseSemantics
Firebird Home Firebird Home Prev: MaxUserTraceLogSizeFirebird Documentation IndexUp: Configuration Parameter Additions and ChangesNext: RemoteAuxPort For Classic and Superclassic

OldSetClauseSemantics

D. Yemanov

Before Firebird 2.5, the SET clause of the UPDATE statement assigned columns in the user-defined order, with the NEW column values being immediately accessible to the subsequent assignments. This did not conform to the SQL standard, which requires the starting value of the column to persist during execution of the statement.

Now, only the OLD column values are accessible to any assignment in the SET clause.

The OldSetClauseSemantics enables you to revert to the legacy behavior via the OldSetClauseSemantics, if required. Values are 1 for the legacy behaviour, 0 (the default) for the corrected behaviour.

Warning

  • Changing this parameter affects all databases on your server.

  • This parameter is provided as a temporary solution to resolve backward compatibility issues. It will be deprecated in future Firebird versions.

Prev: MaxUserTraceLogSizeFirebird Documentation IndexUp: Configuration Parameter Additions and ChangesNext: RemoteAuxPort For Classic and Superclassic
Firebird Documentation IndexFirebird 2.5 Release NotesConfiguration Parameter Additions and Changes → OldSetClauseSemantics