Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: Db2, Oracle, SQL Server

Re: Db2, Oracle, SQL Server

From: Noons <>
Date: Wed, 09 Feb 2005 19:20:10 +1100
Message-ID: <4209c7b3$0$10186$>

Serge Rielau apparently said,on my timestamp of 9/02/2005 12:47 AM:
> Noons, where is IBM critizing multi-version read consistency?
> Speaking for myself (which is all I can do) please point me to where I
> use the words "better" or "worse"? There is no such thing as a free
> lunch however, and that is what is often forgotten by some posters.
> And if pointing that out is criticism, I'll carry that burden.

I meant criticism as in academic, informed one. The kind that knowledgeable people do. I think it should be done and I have no problem with it. Long overdue, there are some aspects of Oracle row locking that I feel could be improved. That will require someone external to push the right buttons, so to speak. Uninformed marketing crap though, gets my fur rubbed the wrong way. I'm too old to change now.

> on. DB2 from release to release get's more subtle about locking while
> Oracle is reliefing the burden of managing rollback segments.

Yup, very much so.

> Correct, locking is the means to the end of isolation level.
> It is isolation level that an App developer designs for and it is
> locking that a developer works around ;-)

App designer. Developers rarely design, they just follow instructions. But, agreed.

> Apparently the industry believes they are all needed, including multi
> version.

"The industry" is thick as a brick. J2EE is the best proof. ;)

> Hard to believe you falling for MS vapor ware ;-)

Sure. Problem is: I've got no reason to doubt this one. Allow me to keep for myself why.


Sorry: secure and won't let me in without rego. But I take your point. Like I said: informed criticism and healthy competition can only result in mutual improvement. Nothing wrong with that.

Nuno Souto
in sunny Sydney, Australia
Received on Wed Feb 09 2005 - 02:20:10 CST

Original text of this message