Orchid XP v8 wrote:
> In other words, you save a little bit of code, and lose almost 
> everything that makes databases useful. 

You can gain performance in certain circumstances. For example, if you look 
at "memcached", it's basically an OO database that serves as a front end to 
relational databases, except you have to manage it manually. An OODB for the 
right problem can be much more scalable *because* you lose the ability to 
search.

> Unrelated, but... it seems, intuitively, that functional programs should 
> be a much better "fit" to the relational model.

Yeah. I was thinking that. Imagine STM monoid values that don't disappear 
when your program exits, for example. Sort of the same idea...

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message