Greeting everyone...
Yes, i'd be curious too! I see MVC and OODB/SQLDB as completely
orthogonal concepts.
Plus, if I may add, the distinction between OODB and relational can in
practice not always be so clear. In fact I know of two efforts that try
to combine the benefits of both these worlds, i.e of combining real
objects with a "tabular" organization.
One of these is the moellus package, that is a layer on top of the
small Durus OODB (that is a ZODB-inspired OODB, but intentionally
simpler), that organizes items (objects) in containers (tables). The
package allows you to define an object model, similar to an ORM.
However, you can think of this as an ORM without the mapping layer, as
your model *is* your database. Other advantages you get for free are
real object references, as well as typically difficult-to-have features
such as "mutable compound primary keys". Moellus is at:
<http://ruggier.org/software/moellus/>
The other one I know of is Schevo from Orbtech. There may well be
others, but my point is which back-end you use has, or should have,
nothing to do with how you organize your user application.
mario
On Nov 20, 2005, at 11:45 AM, Cheng Zhang wrote:
I am curious to learn more about why "object DBs are not good fit for
the MVC-like separation". Previously I had very basic exposure to
ZODB, along with the concept of object database, when I played with
Zope a bit years ago.
Thanks.
- Cheng
On Nov 20, 2005, at 1:12 PM, Tom Tobin wrote:
ZODB is an object database, not a relational one; based on my
experience with it and other object DBs, it's not a good fit for the
MVC-like separation Django adheres to.
