|Subject||Re: [firebird-support] After update trigger: the same values for new.somefiled and old.somefield|
Would it be possible that the original update triggered a second update on the same record, hence the value of new and old are the same? For instance a trigger after update calls a procedure to update the same record, the first run of the trigger will have old <> new, but perhaps on the second run, triggered by the SP, the value of old would be the new value on the first execution of the trigger, and the value of new on the second execution may be the same as old if that field has not changed on the SP. Is that possible?
----- Original Message -----Sent: Saturday, August 27, 2016 8:04 PMSubject: [firebird-support] After update trigger: the same values for new.somefiled and old.somefieldHello,
shouldn't the values of new.somefield and old.somefield be different in an after update trigger, when the value of that field has definitely changed?
For some reason they both have the new value and I can't figure out why. If I didn't misread all the articles, I've found, completely, then they should be different, shouldn't they?
I'm using Firebird 126.96.36.199539.