On Sun, 2007-28-01 at 23:56 -0500, Mark Ramm wrote: > We talked about this a bit at the TurboGears Jam a couple of weeks > ago. Really interesting stuff. > > When we talked about it John raised a good point which I think is > worth making here. > > One issue to consider is the speed of (de)serialization of complex > objects. If you have huge multi-megabyte objects you can get > significant performance gains with an OODB if it is well optimized. > To save the same object to a relational database your ORM is going to > have to do millions of little type conversions, and that can be > expensive. > > ORM's give you flexibility in how you query your data, and are > generally faster at cross-object queries than their Object Database > counterparts. Generally this is enough to keep me using Relational > Databases. > > But even though OODB's haven't caught on the way many had hoped, they > can still be the right choice for a variety of applications -- > particularly when you have a well understood picture of how your data > is going to be used.
Just out of curiosity ( as I have done only very minimal reading on OODB's ), would there likely be a difference in performance in cases where you are building a lot of hierarchal trees using recursive functions and self-referencing foreign keys? I sometimes wonder whether the techniques I using to build auto-generated dom trees for menus are perhaps really inefficient at the db layer ... :/ Thanks for the interesting thread though! Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
