Re: Unknown SQL

From: Carl Rosenberger <carl_at_db4o.com>
Date: Sat, 21 Jul 2001 23:27:27 GMT
Message-ID: <9f44gm$go2$03$1_at_news.t-online.com>


Bob Badour wrote:
[table structure, cascading deletes, object-relational layer]

> >There are lots and lots of paradigms to learn here.
> >Are they all necessary?
>
> Huh? Whenever I see anyone use the word "paradigm" my bullshit antennae go
> on full alert.
 

:-)
Bullshit-Bingo?

Can I replace "paradigm" with "concepts"?

> There are no "paradigms" to learn. There are some data management  principles
> to learn -- a principled approach always outdoes an unprincipled approach  by
> every measure. Relational is simplicity itself.

Now that sent me falling off the chair laughing. Some examples of simplicity:

  • fetching the last generated pkey on ORACLE in a multi-user environment: SELECT table_sequence.currval FROM dual
  • stored procedures: the place for misplaced object business rules, incompatible between vendors
  • triggers: dito
  • outer joins: no standard yet
  • subselects: On ORACLE subselect always needs to be on the right side of "=" expressions. Why? Query optimization is disabled.
  • isolation levels: no standard whatsoever
  • views: vendor specific soup
  • object-relational mappers: horribly expensive, buggy and slow
  • strings limited and fixed in length. Maximum length of 2000 characters ?
  • blobs one blob per table? hahaha :-)
  • JDBC - ODBC - native drivers: what performance do you expect, if you convert data 17 times?
  • date formats: Madame Tussauds
  • case sensitivity in table names turn the key in MSSQL and you can reengineer 3 manyears
  • knowing the number of rows in a resultset: why bother?
  • rollback segment overflow Oh yeah? What's that?
  • referential integrity violation ???
  • cascade-on-delete What do you do, if two references to the same child are possible?
  • cascade-on-copy Have you ever watched a relational database bite it's tail?

Sorry, at this time of day (2:46) I usually drink some wine. If you are seriously interested, I could bring up 50 more examples of complexity tomorrow. Industrial relational databases are anything but simple.

Kind regards,
Carl

---
Carl Rosenberger
db4o - database for objects - http://www.db4o.com
Received on Sun Jul 22 2001 - 01:27:27 CEST

Original text of this message