I would agree, since you seem to know RDBMS already. Use ZODB for metadata and other types of objects. This approach also allows access to the data from other, external applications. Or go with whatever gives you the "cleanest" application design. One of the things Python & Zope emphasize is that it's not about the raw numbers, it's all about ease of use, rate of development/deployment, application of logic, etc. Samir. And this is of course, just my $0.02. -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Tuesday, March 11, 2003 01:33 To: mlong@datalong.com Cc: Zope Subject: Re: [Zope] ZODB vs Relational Databases Michael Long wrote at 2003-3-10 09:05 -0500:
Please forgive me if this is in a FAQ somewhere. I am writting an application that will be capturing financial information. If I use the ZODB and create expense and income objects to capture this information there will over a 1000 objects added a week. I will be tracking history, archiving data, etc. Is Zope the right tool for this type of application or am I better off creating the objects that this data is associated (companies, people, properties, etc) within the ZODB and using a relational database such as PostgreSQL to track the higher volume financial data.
If I have lots of highly structured data, I would go for a relational database and not store them in the ZODB. Dieter _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )