My ZSQL product has a very simple feature for hooking up up to
memcache but with one caveat: that you can't invalidate the cache.
It only works for selects of course but it's really easy to work with. E.g.
SQLSelectAverageUserAge(min=10, max=20, memcache__=True)
(defaults to 5*60 seconds)
...or..
Thanks for your suggestions, Andreas.
Any chance these are going to work under Zope 2.8?
Regards
Marco
On Fri, Aug 1, 2008 at 4:04 PM, Andreas Jung <[EMAIL PROTECTED]> wrote:
>
>
> --On 1. August 2008 15:55:41 +0200 Marco Bizzarri <[EMAIL PROTECTED]>
> wrote:
>
>> Hi all.
>>
>> I have a zope app
--On 1. August 2008 15:55:41 +0200 Marco Bizzarri
<[EMAIL PROTECTED]> wrote:
Hi all.
I have a zope application which uses a db (postgreSQL) to store and
retrieve data. I would like to cache it.
It is ok for me to cache them on thread-base. Up to now I've used a
simple _v_ attribute, with a
Hi all.
I have a zope application which uses a db (postgreSQL) to store and
retrieve data. I would like to cache it.
It is ok for me to cache them on thread-base. Up to now I've used a
simple _v_ attribute, with a dictionary.
The approach works, but:
- the _v_ attribute is not transactional (an