Subject | Re: [firebird-support] UPDATE and SQL conformance |
---|---|
Author | Dmitry Yemanov |
Post date | 2008-12-04T10:00:56Z |
lacakus wrote:
Starting with v2.5 Beta, FB will behave correctly by default, but you
can revert back to the legacy mode via firebird.conf.
Dmitry
>Accordingly to the SQL specification, this is wrong.
> I encounter following situation (problem?):
>
> update table1
> set column1=value1, column2=column1
> where ...
>
> When I run this statement in Firebird (also in MySQL), evaluation and
> assignment of each <set clause> is done sequentialy, so at the end of
> statement column2 equals to value1
> When I run this statement in MS SQL Server, right sides of each <setThis is correct.
> clause> are evaluated first and assignment is done after, so at the end
> of statement column2 equals to original "OLD.column1"
Starting with v2.5 Beta, FB will behave correctly by default, but you
can revert back to the legacy mode via firebird.conf.
Dmitry