Ben Sizer wrote: > GinTon wrote: > > 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. > > What OODBMS people call 'a disconnect', other people often call > 'abstraction' or 'a clean, minimal interface'. >
That is a blessing/curse of working with a relational database. No matter how much you try to abstract away SQL, past a certain complexitly level you will have to use it. I doubt that there is an ORM system available today that can handle complicated queries as well as a human. Usually I view encounters with the object-relational disconnect as an opportunity to learn more about SQL, and a way to legitimately let myself play the optimization game for a while. Obviously if you look at it as nothing but a burden it will always be one. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
