Sybase vs Oracle, what a load of CRAP!

The level of argumentation from the non-ORACLE supporters nowadays seems to have gone downhill.

Cursors are bad in a RDBMS? Er? Excuse me? Which world do you live in? <VBL, ROFL>

Row locking is not needed? Boy, this one reminds me of the interminable arguments from the Ingres camp when ORACLE didn't have true row locking and Ingres had "promotable row locks" (whatever that could be of use for...).

ORACLE doesn't have inbuilt mechanisms to look at its own dictionary and internal tables? How about SQL itself? See, ORACLE is the ONLY RDBMS out there that obeys one of the 12 rules of Codd: the one about the database engine not subverting itself and allowing "backdoor" access to internal structures. SQL access to the ORACLE dictionary has been there since V3, for Pete's sake!

How about the 2K block size in Sybase/SQLServer? That is NOT a limitation? What next?

The fact is, boys and girls: when ORACLE doesn't have the feature, then it's a crime. When they do, then it's not needed.

WHAT A LOAD OF CRAP! It makes me sick that in this day and age we still have discussions at this level of incompetence, lack of knowledge and lack of real life experience.

It's funny how these ones are always cross-posted. Can't these ass-holes stay in their little neck of the woods and keep their blasted discussions about the length of their intelectual manhood out of this NG?

--
Cheers
Nuno Souto
D.C.S. P/L
e-mail: nsouto_at_acay.com.au Received on Sun Nov 22 1998 - 08:01:03 CST