Along with everyone's take: A simeple rule (maybe too simple) would be if it is highly relational data put in a SQL database and call it. If it is better nested (object oriented data) that could benefit from all of the security, through the web editing and other such fine Zope features put it in Zope. EX: NFL data, teams, players, seasons = SQL EX: Directory of addresses, locations, shops = ZODB There are also things that Zope can and will handle better with Zope products that you would have to build from scratch if you used an SQL database and I think that is why they say to use it if you already have it. The other consideration is size... while Zope can handle a TON of data (objects) if you are talking millions of items (rows) you might want to throw it in a SQL database. BZ
I'm coming to Zope from PHP where my database is MySQL. However I am wanting to move to Zope and am trying to learn the correct way of working in this platform. I know that I can connect to MySQL from Zope but from what I read it appears that the use of this feature is recommended only if one is wanting to use an existing database. Since I am starting a new Zope application, and will be creating new data files, is it better to use MySQL or ZODB to handle form data?
I would really appreciate hearing from experienced Zope users on this matter.
Paul
_______________________________________________ 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 )