From experience, I'll say that an OODBMS is not an obvious win. As with anything there are tradeoffs. Generally speaking, the model is nice and the ZODB is even a decent implementation. But RDBMSes remain more mature. Certain types of queries are a lot easier to arrange and schema migration is a tackled problem.
This is why I lean toward SQLAlchemy these days. It exposes a good amount of power at both the python object and RDBMS sides of the equation. By the way, turbogears.database.run_with_transaction is a generic function. This means that you can fairly easily plug in your own implementation of that. Kevin On Aug 30, 2006, at 6:10 AM, GinTon wrote: > > I have seen that for web applications is best far using a ODBMS: > > 1- Objects in an OODBMS can store an arbitrary number of atomic types > as well as other objects. The fact that an OODBMS is better suited to > handling complex,interrelated data than an RDBMS means that an OODBMS > can outperform an RDBMS by ten to a thousand times depending on the > complexity of the data being handled. > > 2- Data in the real world is usually has hierarchical characteristics. > The ever popular Employee example used in most RDBMS texts is > easier to > describe in an OODBMS than in an RDBMS. > > 3- A query language is not necessary for accessing data from an OODBMS > unlike an RDBMS since interaction with the database is done by > transparently accessing objects. It is still possible to use > queries in > an OODBMS however. > > 4- In a typical application that uses an object oriented programming > language and an RDBMS, a signifcant amount of time is usually spent > mapping tables to objects and back. This "impedance mismatch" is > completely avoided when using an OODBMS. > > 5- The user of an RDBMS has to worry about uniquely identifying tuples > by their values and making sure that no two tuples have the same > primary key values to avoid error conditions. > > 6- With an RDBMS it is not possible to model the dynamic operations or > rules that change the state of the data in the system because this is > beyond the scope of the database. With an OODBMS there is no > disconnect > between the database model and the application model because the > entities are just other objects in the system. > > > http://www.kuro5hin.org/?op=displaystory;sid=2001/5/3/32853/11281 > http://www.odbms.org/introduction_whenODBMS.html > http://en.wikipedia.org/wiki/Object_database > > > > -- Kevin Dangoor TurboGears / Zesty News email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
