On Fri, Feb 16, 2001 at 10:56:23AM +0800, Bak@kedai wrote:
If your query is pretty much the same query over and over (like a main webpage query), you should turn query caching on on the advanced tab for your ZSQL query. This will tremendously speed up accesses, and leave your db available for queries which can't be cached (searches etc). If you're worried about missing an update, set the cache time low to say 60 seconds, if you're happy to wait 5 mins, set it to 5 mins. All queries with the same arguments will come out of the cache.
i have tried this with ZPyGresDa, and it doesn't work well. some users will get a cache not found error. can' t really remember the real error message. but this was quite sometime back, during zope-2.1 era.
haven't tried it yet with zope 2.3, or even with PoPy.
This sounds like the cache entry bug that was squashed in 2.2.5b1: - The ZSQLMethods code to handle query caching had a bug that could cause a KeyError in certain cicumstances. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------