On 11/20/05, bruno modulix <[EMAIL PROTECTED]> wrote: > Only data are saved to the zodb.
But you're still working with it solely in the form of a Python object (with aforementioned methods and all). With a SQL DB, you can access that data in a variety of ways, move it to a different database implementation, and you're not tied specifically to Python and the ZODB. > > I also find changing a > > model under an object database to be messier than changing one with a > > relational database. > > This has nothing to do with MVC. As for the "mess", it depend on what > you are changing and how your object graph is structured. I'm sorry if it seemed I was implying it was directly related to MVC; it was more of an "aside" with regards to another perceived disadvantage. > > Overall, I prefer the clearly delineated > > separation a relational database provides between my data and what I'm > > using it for. > > > > And ? Is that all you have to support your previous assertions ? "C'est > un peu court, jeune homme". No, it's merely a conclusion. (And I fear I'm ignorant of languages other than English. :-) )
