[SQLObject] Expiring Cache

[Sidnei da S. <si...@aw...>]

Howdy again,

I am in the process on getting the Zope3+SQLObject integration to the
next level, which is optimization. I haven't started profiling yet,
but one of the things that I would like to try is to enable cache on
SQLObject (I disabled it since the start because it was getting too
much in the way) and hook with the event system in Zope 3 to process
cache invalidation when an ObjectModified message comes
through. However I am not sure about the way the SQLObject.expired()
method is implemented. It seems that it is doing a bit more than
expiring the cache, it is also marking the object as expired and
removing something from the instance which I'm not sure what it
is. The way I see it, I should probaly call expired() which would
mark the object as expired and clear the cache for that object. On the
first attribute access after that, SQLObject would find the cache is
empty, fetch the live values from database and remove the expired mark
from the object. Maybe a revalidate() method on SQLObject could do it,
to make it simpler. Am I close?

[]'s 
-- 
Sidnei da Silva <si...@aw...>
dreamcatching :: making your dreams come true
http://awkly.org

When Dexter's on the Internet, can Hell be far behind?"