Hello Sean,

>>> 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 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.

Right. Perhaps NEW is changed to OLD?

>
> 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.
  • [firebird-supp... patrick_mar...@yahoo.com [firebird-support]
    • Re: [fire... Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
      • Re: [... patrick_mar...@yahoo.com [firebird-support]
    • Re: [fire... fabia...@itbizolutions.com.au [firebird-support]
    • Re: [fire... Thomas Steinmaurer t...@iblogmanager.com [firebird-support]
      • RE: [... 'Leyne, Sean' s...@broadviewsoftware.com [firebird-support]
        • R... Thomas Steinmaurer t...@iblogmanager.com [firebird-support]
          • ... 'Leyne, Sean' s...@broadviewsoftware.com [firebird-support]
            • ... setysvar setys...@gmail.com [firebird-support]
              • ... patrick_mar...@yahoo.com [firebird-support]
                • ... Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
                • ... Helen Borrie hele...@iinet.net.au [firebird-support]

Reply via email to