mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-23 02:03:04 +01:00
Fixed CORE-903: Update Field update / result Updated.
This commit is contained in:
parent
0a02a59f3d
commit
99402ef337
@ -337,6 +337,29 @@
|
||||
#
|
||||
#OldColumnNaming = 0
|
||||
|
||||
|
||||
# Prior to 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. Starting with Firebird 2.5, only OLD column
|
||||
# values are accessible to all the assignments of the SET clause.
|
||||
#
|
||||
# Example of the old vs new behaviour:
|
||||
#
|
||||
# UPDATE T SET A = B, B = A
|
||||
# old result: A gets equal to B, B doesn't change
|
||||
# new result: A and B get their values exchanged
|
||||
#
|
||||
# Change this configuration option to 1 (true) only if your SQL code relies
|
||||
# on the legacy semantics of the SET clause. It's provided as a temporary
|
||||
# solution for backward compatibility issues and will be deprecated in the
|
||||
# future Firebird versions.
|
||||
#
|
||||
# Type: boolean
|
||||
#
|
||||
#OldSetClauseSemantics = 0
|
||||
|
||||
|
||||
# ----------------------------
|
||||
# Relaxing relation alias checking rules in SQL
|
||||
#
|
||||
@ -362,6 +385,7 @@
|
||||
#
|
||||
#RelaxedAliasChecking = 0
|
||||
|
||||
|
||||
# ----------------------------
|
||||
# Client Connection Settings (Basic)
|
||||
#
|
||||
|
Loading…
Reference in New Issue
Block a user