News for hackers. Stuff that matters.
Re:Relational databases performed a task that didn't need do... by xenoterracide on Monday November 23, 2009 @03:26PM (#958059)
"With the recent arrival of object-oriented databases, the industry may finally achieve some of the promises which were made 20 years ago about the capabilities of computers to automate and improve organizations."

um... wow... this 1 sentence discredits the entire email. Object Oriented Databases were a HUGE failure. I can't be sure but PostgreSQL might be the only surviving one, and it survived because it went relational. just my 2 cents.

Re:Relational databases performed a task that didn't need do... by sfwc on Monday November 23, 2009 @03:45PM (#958093)
GemStone was beloved of most who used it, and it is poised to make a comeback through MagLev.

Meanwhile, ORMs (which attempt to implement an OODB on top of an RDB) are ubiquitous.

Re:Relational databases performed a task that didn't need do... by shiro on Monday November 23, 2009 @06:31PM (#958375)
This article becomes interesting if you realize that (1) it was written in 1991 and (2) was written by a distinguished computer scientist. I think it amusing to see how smart people were thinking back then.

I built a system with OODB back in late 90s. It was a pleasant experience in a way; I could walkaround inflexibility of RDBMS. RDBMS works great if your data domain can be straightforwardly represented in relational model. But if your application is inherently working on a graph, it becomes awkward to map it onto relational model. With OODB, graphs formed by objects can be directory stored.

OTOH, I had a difficulty from the lack of good abstraction; ironically, implementaion of application data structure was too tightly coupled with the data storage model. Application-level implementation details could affect data storage unnecessarily, or some optimization techniques in the db side could affect the application. Relational model and SQL do give a good abstraction barrier in a sweet spot, at least for some type of applications.

I think graph database will give us this nice abstraction barrier for the network-of-object type application domain. Let's see how it turns out in 20 years later...

Re:Relational databases performed a task that didn't need do... by jbooth on Monday November 23, 2009 @03:30PM (#958066)
No it doesn't.. ok, early 90s, people thought object oriented everything was the way forward.

But his main point, that blasting through a flat file without a ton of row-locking and transactional overhead could satisfy a number of needs better than the actual DBMS, is still true.

If you need to be transactional, on the other hand, that's a different story.

Re:Relational databases performed a task that didn't need do... by simc on Monday November 23, 2009 @05:52PM (#958316)
PostgreSQL was not an object-oriented database, it was an object-relational database. Despite not living up to some people's exceptions that that it would replace the relational database object-oriented databases were not a "huge failure". They are useful for applications where relational databases were not suitable, for example CAD (as mentioned in the article).
Re:Relational databases performed a task that didn't need do... by rapind on Monday November 23, 2009 @03:42PM (#958085)
What's the difference between object oriented and document oriented databases?

Aren't all of the recent key/value databases lately pretty much the same concept as an object database?

Sorry if that's a dumb question...

Re:Relational databases performed a task that didn't need do... by wmf on Monday November 23, 2009 @04:25PM (#958181)
OODBs tend to use navigation of object graphs (see http://c2.com/cgi/wiki?NavigationalDatabase ) as the key operation, while document or key-value DBs rely more on queries.
Re:Relational databases performed a task that didn't need do... by rapind on Monday November 23, 2009 @07:23PM (#958452)
Thanks for the link. Dug around a bit and from what I can tell they are pretty similar. Object databases have been referred to as hierarchical databases (I.e. XML data), many of the key-value databases being touted in the past couple of years seem hierarchical to me, only with some additional indexing and query language packaged on top (which you could add yourself with Lucene or Sphinx I would assume).

I must be missing something, but I'll keep digging.