<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2003/07/dcc51ef8d1c6e45c40c7ae94ca217a7e"
  from="Seth Kurtzberg &lt;seth@c...&gt;"
  author="Seth Kurtzberg"
  date="2003-07-05T22:16:02"
  subject="Re: [OT] OODBs (was Re: [Caml-list] Ocaml Object-Oriented database?)"
  prev="2003/07/abedd2bc380702d21894543bdb16f750"
  next="2003/07/bb08176385e0e3626d7033d67ea11fa8"
  prev-in-thread="2003/07/abedd2bc380702d21894543bdb16f750"
  prev-thread="2003/07/abf5ceeae667fb34e9e077ec470362fb"
  next-thread="2003/07/ce2eb56d389991d2a9c2107a035618d4"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="[Caml-list] Ocaml Object-Oriented database?">
<msg 
  url="2003/07/6d54ebe42cd1491a5c32cf6e278324db"
  from="Sadruddin Rejeb &lt;lists@m...&gt;"
  author="Sadruddin Rejeb"
  date="2003-07-05T15:59:22"
  subject="[Caml-list] Ocaml Object-Oriented database?">
<msg 
  url="2003/07/3388342994685b74d407a480e416b20b"
  from="Seth Kurtzberg &lt;seth@c...&gt;"
  author="Seth Kurtzberg"
  date="2003-07-05T19:30:01"
  subject="Re: [Caml-list] Ocaml Object-Oriented database?">
<msg 
  url="2003/07/abedd2bc380702d21894543bdb16f750"
  from="Matt Gushee &lt;mgushee@h...&gt;"
  author="Matt Gushee"
  date="2003-07-05T20:41:17"
  subject="[OT] OODBs (was Re: [Caml-list] Ocaml Object-Oriented database?)">
<msg 
  url="2003/07/dcc51ef8d1c6e45c40c7ae94ca217a7e"
  from="Seth Kurtzberg &lt;seth@c...&gt;"
  author="Seth Kurtzberg"
  date="2003-07-05T22:16:02"
  subject="Re: [OT] OODBs (was Re: [Caml-list] Ocaml Object-Oriented database?)">
</msg>
</msg>
</msg>
</msg>
</thread>

<contents>
On Sat, 5 Jul 2003 14:41:16 -0600
Matt Gushee &lt;mgushee@havenrock.com&gt; wrote:

&gt; On Sat, Jul 05, 2003 at 12:29:56PM -0700, Seth Kurtzberg wrote:
&gt; &gt; 
&gt; &gt; I've done some work in this direction, although with an object-relational database, not an OODB.  I'm convinced that the OODB concept is fatally flawed.
&gt; 
&gt; I've heard this statement before, but most of the explanations I've heard amount to "been there, done that, didn't work." What is wrong with OODBs, in your opinion?

They don't deliver what they promise.  The basic idea is to make programming with persistent objects similar to programming with ordinary objects.  But the complexities involved with implementing OODBs requires you to code in sub-optimal ways.

To abandon a well established technology such as RDB, you need a reason why the newer method is better, so you need to justify the use of the OODB paradigm in some rational terms:  productivity, reliability, ease of maintenance, etc.  The OODB products I've used simply don't deliver this.

The object/relational hybrid is a much better option as it leverages 25 years of R&amp;D in the database community. 

&gt; 
&gt; -- 
&gt; Matt Gushee                 When a nation follows the Way,
&gt; Englewood, Colorado, USA    Horses bear manure through
&gt; mgushee@havenrock.com           its fields;
&gt; http://www.havenrock.com/   When a nation ignores the Way,
&gt;                             Horses bear soldiers through
&gt;                                 its streets.
&gt;                                 
&gt;                             --Lao Tzu (Peter Merel, trans.)
&gt; 
&gt; -------------------
&gt; To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
&gt; Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
&gt; Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
&gt; 


-- 
Seth Kurtzberg
MIS Corp
480-661-1849
seth@cql.com

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners

</contents>

</message>

