On 23 Jun 2003 at 14:01, Tim Ledgerwood wrote:

>> You shouldn't set ALL transactions' isolation level to
>> concurrency.
>
>Why?

Oh, I'm afraid I misinform you. I mixed up concurrency and
consistency and even then I did a mistake.
All concurrency transactions is Ok. It produces no conflicts if one
of transaction is read-only and the others update different records.
I just keep to rule: use the lowest possible isolation level.

Look at ApiGuide -> Working with transactions -> isolation level
interactions.

SY, Dimitry Sibiryakov.