I might suggest that designing an application without knowing for sure what platform you will be using is a recipe for disaster. Decide whether you will be using Zope or not *before* you build the whole app. That said, I think the extra work in storing content in the database will only be worth it if you know that other applications besides zope will need direct access to it through a SQL interface. Even if you store all your content in Zope objects (which has many advantages IMHO), you can easily access it externally using XML-RPC. OTOH, if you choose to use a relational back-end, you should check out the DBObjects product. I have not myself used it, but I think it is ained right at solving this problem. -Casey mike gallagher wrote:
Hi all, I'm about to start an intranet project using Zope. I'm new to the tool but am really excited about using it.
Two questions: 1. Is it good practice to store all my content (press releases, news stories etc) in an external relational database? I think this will ensure that if the company decide to get rid of Zope, it'll be easier to re-use the content. Is this overkill? Is it easy to export content from the Zope OO database into a relational db? (Yes,I'm a newbie!)
2. Anyone have any experience/opinions of using Documentum as a data source?
Thanks in advance!
===== Best regards, Mike Gallagher
__________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://http://taxes.yahoo.com/
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )