|Subject||Re: [Firebird-Architect] "Write Committed" transaction mode|
30.11.2010 7:06, Dmitry Yemanov wrote:
>> Update, delete, and select for update wait if there's aPerhaps, you'll find this discussion interesting:
>> newer version of the record than the transaction can see,
>> then succeed when the transaction that created the
>> newer version commits.
> So it differs from our read-committed mode in the fact that it
> overwrites the data after a concurrent commit, not throw an update
> conflict as we do. Did I get it right? This has been mentioned a few
> times and I do agree it can be useful in various usage scenarios.