Austin Ziegler wrote:
> 
> There are three fundamental problems with OODBMSs

Maybe four.  Austin mentions poor indexing, searching limited by 
navigation, and resistance to change.  I would throw in another issue 
that may be more related to particular implementations, but so far I've 
seen it in every OODBMS.

That problem is granularity of data access.  With an OODBMS, the minimal 
unit of access is the object.  If your design needs large objects with 
many fields, you get to load large objects all the time.  With a RDBMS, 
the unit of access is an arbitrary subset of columns in a row.  The 
impact of this difference on real-world performance can be orders of 
magnitude, and there's little you can do other than redesign your system 
from the ground up to make it more "compatible" with your particular 
OODBMS's philosophy.

> OODBs are crap -- and always will be.

Ah, how do you _really_ feel? :)

-- 
Glenn Parker | glenn.parker-AT-comcast.net | <http://www.tetrafoil.com/>