At 07:37 PM 08-02-02 +0100, you wrote:

>I have found a problem with TIBOTable and TIBOQuery if pessimisticLocking
>are set.
>I have some trigger for trace all the operation on my tables (like
>IBO$DMLCACHE in Survey Application) if PessimisticLocking is true and one
>record is Edited then i see the trigger called 2 times (like 2 Edit/Post on
>the same record). If pessimisticLocking are false all work fine and only one
>update are triggered.

A correct observation. If you are using PessimisticLocking, you must modify any triggers that will be affected by the locking mechanism to prevent them from firing when the client sends the P.L statement across. P.L. is a client-side mechanism - the DB engine itself doesn't support P.L. internally.

>Insert and Delete operation work fine alwais.

Inserts are never affected by P.L. since they are new and therefore won't be visible in the database until the transaction is committed.

Deletes ARE affected, so any Delete triggers do need to considered.


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at www.ibobjects.com