| Subject | Re: [firebird-support] After update trigger: the same values for new.somefiled and old.somefield |
|---|---|
| Author | setysvar |
| Post date | 2016-08-28T15:22:55Z |
Den 28.08.2016 12:55, skrev 'Leyne, Sean' Sean@...
[firebird-support]:
did INSERT and not UPDATE. That way, two new rows after the update would
indicate that somehow something was interfering and modifying the value.
Another thing to check is if there's any trigger on the table that the
AFTER UPDATE trigger is actually updating.
Set
[firebird-support]:
>>>>> I'm using Firebird 2.5.2.26539.For testing, I think it would be preferable if the after update trigger
>>>> 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.
>>
>> Right. Perhaps NEW is changed to OLD?
> Patrick??
>
> Please confirm the problem details.
>
>
> Sean
did INSERT and not UPDATE. That way, two new rows after the update would
indicate that somehow something was interfering and modifying the value.
Another thing to check is if there's any trigger on the table that the
AFTER UPDATE trigger is actually updating.
Set