At 09:38 AM 12-09-01 +0200, you wrote:

>I have a question concerning the locking mechanism.
>I set the pessimisticlocking of an ib_query to true. Then I have for
>example the following situation:
>
>A table defined like that:
>
>CREATE TABLE BAN (
> BAN_ID AUTOINC,
> KURZ DOM_C15 NOT NULL,
> NAME DOM_C40 NOT NULL,
> BLZ DOM_C10,
> KTO_NR DOM_C20,
> BH_KTO_NR DOM_C20,
> TS_USR_ID DOM_TS_USR,
> TS DOM_TS);
>
>the sqlstatement for the ib_query is for example:
>
>select kurz, name from ban where ban_id = 1;
>
>then I set it to edit mode by calling:
>ib_query1.edit;
>
>Now my question: is it right, that not only the 2 selected fields are
>locked for other transactions?
>It must be, because when I try to make chages to for example BLZ, I
>get a lock error.
>
>I thought, that IB only locks the selected columns.

No, there is no way that a single column can be locked. InterBase has row-level locking.

Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________