Tom Tobin wrote: > 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
Which is exactly what I want. > (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. Moving data from one representation to another is not that big a problem if needed - and my experience with RDBMS is that portability between various vendors is still a fairy tale unless you restrict yourself to the smaller common SQL subset. Anyway, for this project, if I have a need for data exchange, XML will certainly be a better format. > >>>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 did, since you were replying to a question about your previous assertion on OODB "not being a good fit for MVC". > it was more of an "aside" with regards to another perceived > disadvantage. "perceived" is the key, I think. > >>> 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. :-) ) > fr->en : "It's not enough, young man" !-) -- bruno desthuilliers développeur [EMAIL PROTECTED] http://www.modulix.com
