durusmail: durus-users: OODB vs SQL
OODB basics
2005-10-08
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-09
2005-10-11
2005-10-12
Re: OODB basics
2005-10-11
OODB vs SQL
2005-10-09
2005-10-09
2005-10-09
Re: OODB vs SQL
2005-10-10
Re: OODB vs SQL
2005-10-10
OT: Durus
2005-10-13
2005-10-13
2005-10-13
2005-10-09
2005-10-09
2005-10-09
2005-10-10
2005-10-11
2005-10-11
2005-10-11
2005-10-11
Re: OODB vs SQL
2005-10-11
2005-10-11
2005-10-11
2005-10-12
2005-10-12
2005-10-12
Demo application [was: Re: [Durus-users] Re: OODB vs SQL]
2005-10-13
Re: OODB vs SQL
2005-10-11
Durus basics
2005-10-09
2005-10-09
2005-10-10
2005-10-10
2005-10-10
2005-10-13
2005-10-13
2005-10-13
2005-10-13
Re: OODB basics
2005-10-13
OODB vs SQL
Oleg Broytmann
2005-10-09
On Sun, Oct 09, 2005 at 02:36:03PM -0400, David Binger wrote:
> >OODB disadvantage: the OODB is oriented toward one and only one
> >programming
> >language.
>
> True in practice, but you could use a language-neutral serialization
> if you
> really wanted to.  I'm sure you could load python pickles into some java
> representation if it mattered.

   The point taken.

> >SQL disadvantage: you have to formally describe what subset of rows
> >from
> >what Cartesian product you want to select; you have to select a
> >subset of
> >one row even if you know the direct ID of the row.
>
> That doesn't seem so bad.

   But you have to (mentally) walk away from your programming language to
the relation algebra, construct and filter those Cartesian products...

Oleg.
--
     Oleg Broytmann            http://phd.pp.ru/            phd@phd.pp.ru
           Programmers don't die, they just GOSUB without RETURN.
reply