Applies to
TIB_Dataset

Declaration
Property PessimisticLocking : boolean;

Description
Upon going into dssEdit state you can have a dummy update automatically performed that will lock the record that just went into dssEdit state.

If another user has already opbtained a lock on the record then an exception is raised and the record will remain as readonly.

The dummy update executes against each updatable RECORD on the server of the current row so that the user can be assured that their work will be able to post when they are done with it. I say each updatable RECORD because with IB Objects joined datasets from multiple tables are still updatable.

InterBase is nice because only the exact rows that are updated are locked.

These locks only remain for the duration of the transaction too. Thus, they are cleaned up if a connection failure occurs.