Hi,
I noticed that when using pessimistic locking, the TIB_Query runs dummy
update like this

UPDATE MYTABLE
SET MY_PRIMARY_KEY = MY_PRIMARY_KEY
WHERE MY_PRIMARY_KEY = SOMEVALUE

to lock the row. OK, but as a side effect to this behaviour all Before and
After Update triggers are fired. Then when the user posts the edited
changes, the triggers are fired for the second time.

How to avoid firing the triggers for the first time? The trigger can start
time consuming work and there is no need to to the same work twice.

Thanks for your time
Ales