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 ?

Thanks in advance for any help.
Aldo Caruso