Subject | Re: [Firebird-Architect] "Write Committed" transaction mode |
---|---|
Author | Ann W. Harrison |
Post date | 2010-11-30T16:21:41Z |
On 11/30/2010 5:24 AM, Dimitry Sibiryakov wrote:
statements when it tries to update a record that was updated by a
concurrent transaction. The fact that Oracle is a mess doesn't mean
that all relational databases are a mess, or even that a feature Oracle
does badly can't be done well.
Best regards,
Ann
> 30.11.2010 11:07, Roman Rokytskyy wrote:OK, but InnoDB is open source and well-understood and does not restart
>>> Perhaps, you'll find this discussion interesting:
>>> http://www.sql.ru/forum/actualthread.aspx?tid=809601
>>
>> Just a small note - you cannot really assume that everybody here can
>> read Russian... So, for the sake of good discussion, please make a
>> summary of that discussion.
>
> Summary: Oracle is a big black box with unpredictable behavior in subject area.
>
statements when it tries to update a record that was updated by a
concurrent transaction. The fact that Oracle is a mess doesn't mean
that all relational databases are a mess, or even that a feature Oracle
does badly can't be done well.
Best regards,
Ann