steve summers wrote:

>--- "Ann W. Harrison" <aharrison@...> wrote:
>
>
>
>>At 12:36 PM 9/21/2004, Jonathan Neve wrote:
>>
>>
>>
>>>>The effect is to cause the transaction to fail with
>>>>an apparent deadlock if there are any uncommitted
>>>>records in the data set examined.
>>>>
>>>>
>>>>
>>>>
>>>Are you sure this isn't the behaviour when combined with another TR
>>>option?
>>>
>>>
>>Yes, I'm quite certain that if a read committed no wait transaction
>>encounters a record that has been written (inserted, updated, or deleted)
>>and not committed it will get an immediate deadlock error, whether
>>the transaction that did the write is read committed, snapshot,
>>wait, or no wait.
>>
>>
>>
>>> In my experience, the effect is rather to fail immediately
>>>(without waiting) if any other transaction tries to UPDATE a record
>>>that's already been updated in a different transaction.
>>>
>>>
>>It demonstrably fails with ISQL when attempting to read an
>>uncommitted record.
>>
>>
>>
>
>The answer to this confusion is the "Rec_Version" flag. In IBExpress, if you
>click on the "Read Committed" radio button, you get read_committed,
>rec_version, and nowait flags. The IB6 API Guide says
>
>

That's it. This is the option I was refering to.
I just checked, and sure enough, in the project I was refering to I use
the 'rec_version' flag.

Sorry for clouding the issue!

Jonathan Neve.


[Non-text portions of this message have been removed]