> I've read from "The Firebird Book", page 523, that when setting a
> read committed transaction, the flag RECORD_VERSION is set by default.
> Testing it, I found that it works as if it had the flag NO
> RECORD_VERSION set, because it locks when reading records updated by
> another transaction but not yet committed.
> So I had explicitly invoke "SET TRANSACTION READ COMMITTED RECORD
> VERSION" for avoiding being locked by other transactions.
> Is that true ?

If you are using Firebird 2.5 then use the Trace API to find out what's
really going on.



--
With regards,

Thomas Steinmaurer
Upscene Productions
http://www.upscene.com
http://blog.upscene.com/thomas/

Download LogManager Series, FB TraceManager today!
Continuous Database Monitoring Solutions supporting
Firebird, InterBase, Advantage Database, MS SQL Server
and NexusDB!