On Friday 28 February 2003 07:37 am, Edmund Lian wrote: > 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
Well you said it right there. :) "when the demands of an application are lightweight (and don't require all the good stuff that relational DBs offer)" Some of us have heavyweight demands and want to use all the good stuff. :) But I'll provide more details below... > last night (http://www.amk.ca/zodb/zodb-zeo.html), and was wondering > why people use MiddleKit instead of ZODB. * Object model. * Validation: In the model you specify constraints like enum values, min and max values, etc. MiddleKit will assert these things at run time, which is a nice bonus. * I use the object model for other things like generating forms, tables of objects and detailed object views. It's also great documentation for what my application is tracking/persisting. * See also: http://webware.colorstudy.com/twiki/bin/view/Webware/?topic=MiddleKit * SQL: * I find products like MySQL and PostgreSQL to be exceptionally mature in their documentation, community and support. * Speed: MySQL and Postgres are both ridiculously fast for reading AND writing. * I enjoy being able to use SQL statements when I want to poke around the db directly. * 3rd party tools such as phpMyAdmin, mysqldiff, etc. are ready to go. * Integration. StockAlerts.com uses a PHP/MySQL discussion board. We were able to define some classes in MiddleKit to represent the discussion board tables and make things fit together nicely. > 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 ) I haven't needed transactions or record versioning in my applications. I'm amenable to MiddleKit enhancements in this area, however. > There hasn't been much discussion of using/integrating ZODB/ZEO into > Webware as a standard persistence tool. Am I missing something? Most developers in the Webware community seem married to SQL databases, whether they are using MiddleKit or not. SQL has been around for a long time and even with its flaws it is both mature and fast. There are certainly no technical reasons that would prevent you from using ZODB from WebKit AFAIK. -- Chuck http://ChuckEsterbrook.com ------------------------------------------------------- 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
