> Thomas Steinmaurer wrote:
>> Not here. ;-)
>>
>> * Two concurrent isql sessions
>> * Both start a read committed transaction
>
> That implies NO_RECORD_VERSION where writers block readers...
>
>> * The first isql session does a SELECT * FROM MYTABLE WITH LOCK
>> * The second isql session does a SELECT * FROM MYTABLE (without WITH LOCK).
>> * The second session gets blocked
>
> Not a surprise at all, the same for a regular UPDATE.
>
> Try RECORD_VERSION and see the difference :-)

Right. Thanks. ;-)

To be honest, I wasn't aware that a READ COMMITTED transaction
*defaults* to NO_RECORD_VERSION.

Thanks again.


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com