--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:

> Case is a value expression, not an operator.

Of course... next time I'll try thinking before posting ;-)

> There is a messiness in the Firebird handling of values that will

break

> this particular example. The SQL standard specifies that the values
> used as input to a set operation are the old values, even if new

values

> have been assigned to those fields. Firebird doesn't follow the
> standard in that case, so the set statement that assigns a new value

to

> a will affect the results of the assignment to b.

Is this still the case with Firebird 2.0?

Semp