--- In IBObjects@y..., Enrico Raviglione <e.raviglione@i...> wrote:

> Oops... this behaviour are due to make the Lock on the Edited record?

Exactly! The lock is not a "native" concept of IB, that relies upon transaction and versioning. So to achieve a lock, IBO automatically performs a "dummy update" (something like update mytable set mycol=mycol). But this way the update triggers are fired (something to be considered in some situation).
Regards
Marco Menardi

(btw, visit http://www.cvalde.com/ and read his tech info, very interesting)

>
>
> -----Messaggio originale-----
> Da: Enrico Raviglione [mailto:e.raviglione@i...]
> Inviato: venerdi 8 febbraio 2002 19.37
> A: 'IBObjects@y...'
> Oggetto: [IBO] Bug when TIBO*->PessimisticLocking is set
>
>
> 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.
>
> Insert and Delete operation work fine alwais.
>
> Regards,
> Enrico Raviglione.
>
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/