Re: Flamewar object databases vs. relational databases (was: Unknown SQL)

From: Bob Badour <bbadour_at_golden.net>
Date: 4 Jun 2001 15:47:02 -0700
Message-ID: <cd3b3cf.0106041447.338b50e4_at_posting.google.com>


> >
> > I'll add just one comment:
> >
> > I use a simple criteria: The persistence mechanism dictates what type of system
> > you have, object or relational.
> >
> > If you use a RDBMS then you have a relational system, even if you use Smalltalk,
> > Java, C++ over the top.
> > If you use a pure OODBMS, then you have an OO system.
> >
> > No doubt there are always reasons for choosing any approach and I am not passing
> > judgement. In the end the approach chosen will have advantages and
> > disadvantages.
> >
> > Chris Trathen
>
> This thread is very surprising and it's always the same :-(((
>
> I've done projects with relational- and object-oriented databases
> under Smalltalk and here some points from me:
>
> - it's clear, that OODBMS *can* be superior to RDBMS. No discussion
> about this !

No, network model OODBMS will never be superior to RDBMS. If you really knew what a relational database is, you would see that.  

> - RDBMS are based on a query concept. OODBMS are very strong on the
> navigational concept (though OODBMS can do queeries ...).

The navigational requirement is the primary weakness of network model databases. An RDBMS also supports navigation very well -- it just doesn't require it.  

> - benchmarks showing a tree structure are superior on navigational
> systems, when they use page-server systems and object chaches.

Superior to what? A transitive closure?  

> - when using a rdbms and an OO language noone should really do this
> without a framework.

Actually, I would change this slightly. When using an rdbms and an OO language, one should insist on proper support for domains in the rdbms.

> - oodbms are a good way to give non-database aware programmers a
> persistency system.

Huh? Encouraging programmers to act in ignorance is never a good way to do anything.

> This topic is so difficult: it's sad, that we're talking in such
> a way about this.

This topic is difficult. We have no good solutions for so many issues -- missing information for instance. What I find really sad, though, is how few practitioners even know the good solutions we do have.

Regards,
Bob Received on Tue Jun 05 2001 - 00:47:02 CEST

Original text of this message