One thing I highly recommend is not using zclasses. Learn enough of python products to do a restaurant as a python product. Long term they are more maintainable and more reliable from my experience. I have not been happy with zclasses for many reasons. With the kind of load you will have a python product will probably be best. On 5 May 2001, Arkaitz wrote:
Hi all,
I am starting to design a web app, which will have a database consisting of 5000 to 10000 restaurants, which could potentially grow, but not much more. I'm a newbye to Zope,and initially my idea was to keep all the data in a MySQL DB, and access it from Zope. I need to do some very flexible queries and searches on the DB, and I've found that Z SQL Methods get quite awkward easily. I am thinking now about a pure-Zope (ZOBD) solution. I have thought about using a ZClass for each restaurant and keeping them organized in directories with the next hierarchy: County/City/Restaurant Is this a reasonable idea at all to do? I can write Python, and would like to avoid DTML for non-presentation tasks as much as possible. Also, I would need to be able to do queries of the style "give me restaurants that sell chinese food anywhere in this region/city".
I appreciate any recommendation or resource that can help me make a good decision.
TIA, Arkaitz.
_______________________________________________ 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 )