I have a question... please don't get offended by it, I don't mean it to be offensive...
While I'm not a great fan of object oriented DBs, I do see a role for them in providing persistence when the demands of an application are lightweight (and don't require all the good stuff that relational DBs offer). I was reading one of Kuchling's write-ups about ZODB and ZEO last night (http://www.amk.ca/zodb/zodb-zeo.html), and was wondering why people use MiddleKit instead of ZODB. Why bother trying to persist to a relational DB if you can't really get at the full power of the relational model through MiddleKit (or any other ORM for that matter)? ZODB seems to be rather easy to use, and offers a whole bunch of things that MiddleKit doesn't implement (e.g., transactions, versioning, etc.) ZEO seems to be a neat way to spread work across several Webware instances (so long as the application is read intensive ) There hasn't been much discussion of using/integrating ZODB/ZEO into Webware as a standard persistence tool. Am I missing something? ...Edmund. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
