thecrgrt wrote:

>
> ... I've tried to
> specified a DirtyRead(ReadUncommitted) isolation for starting a transaction
> but there is no effect, for specificed this value with a connection

IIRC the SQL standard allows the substitution of a higher level of
concurrency for a lower level, so Firebird turns dirty read into
Consistency.

One solution would be to write your locking information to an
external table. Concurrency control is not enforced on external
tables. On the other hand, external tables don't support indexes
either, so that method might be a little slow.

Another solution is to reserve the records by making a committed
change.

Regards,


Ann