This level of isolation is table locking, not just records fetched.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

-- We may not have it all together --
-- But together we have it all --

----- Original Message -----
From: "lmirmatos" <lenny@...>
To: <IBObjects@yahoogroups.com>
Sent: Thursday, October 24, 2002 11:46 AM
Subject: [IBO] Transaction with tiConsistency Isolation


> I did an demo project using Employee.GDB with 4 TIBOQuery, 4
> TIBOTransaction, 4 InfoPower wwdbGrids, 1 TIB_Connection.
>
> Transactions are:
> tiConcurrency, tiCommited AutoCommit, tiCommited not AutoCommit and
> tiConsistency.
>
> First 3 transactions worked fine, as explained in help. But the last
> transaction (tiConsistency) not (or may be I don't understood the
> help).
>
> The SQL property of last TIBOQuery was:
>
> SELECT EMP_NO
> , DEPT_NO
> , FIRST_NAME
> , LAST_NAME
> , HIRE_DATE
> FROM EMPLOYEE
> WHERE DEPT_NO <110
>
> tiCommited transactions's TIBOQuery has SQL property:
> SELECT EMP_NO
> , DEPT_NO
> , FIRST_NAME
> , LAST_NAME
> , HIRE_DATE
> FROM EMPLOYEE
>
> When tiConsistency Transaction is active I can't modify any record in
> Employee Table. Is this right? I thinked only those with DEPT_NO <
> 110 should be locked.
>
> Lenny