Re: [SQLObject] Bug in Cache.py

[Mark M. <ma...@di...>]

On Fri, 11 Jul 2003 15:39:52 -0400, Mark Melvin <ma...@di...> 
wrote:

> I have a need to force a refresh of my data from the database. I like the 
> idea of a .sync() function.
>
> At any rate, I have been using the _connection.purge() to force deletion 
> of a certain object from the cache as well as the .clear() method to 
> clear the entire cache.  This caused an exception due to a typo in the 
> .clear() method.
>
> Line 140 should be:	self.expiredCache[key] = ref(value)
>
> Or, change line 139 to use the variable names 'id', and 'obj'.
>

As it turns out - passing cache=False to the connection constructor (as 
mentioned in a previous thread) solves my problem and do not have to use 
these methods anyway...but the bug should be fixed up.

I also noticed if you pass 'cache=False' to the connection and try to call 
.purge(), it causes an exception because there is no 'cache' attribute.  I 
think this should probably be fixed as well with a check or something just 
as simple.

-- 
Thanks,
Mark.