Subject | Re: [firebird-support] After update trigger: the same values for new.somefiled and old.somefield |
---|---|
Author | Thomas Steinmaurer |
Post date | 2016-08-28T08:03:54Z |
Hello Sean,
With regards,
Thomas Steinmaurer
http://www.upscene.com/
Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
>>> For some reason they both have the new value and I can't figure out why.Right. Perhaps NEW is changed to OLD?
>>> If I didn't misread all the articles, I've found, completely, then
>>> they should be different, shouldn't they?
>>>
>>>
>>> I'm using Firebird 2.5.2.26539.
>>
>> Any chance that another trigger is changing the value?
>
> I was thinking that myself, but Patrick said that it was the "old" value which was being changed to the "new" value.
>--
> Another trigger (a BEFORE UPDATE trigger), in a single update operation/chain, can only change the "new" value, nothing should be able to change the "old" value.
With regards,
Thomas Steinmaurer
http://www.upscene.com/
Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.