[Z3-sqlos] obj.destroySelf() broken in sqlos

Andrew Bennetts andrew-sqlos at puzzling.org
Wed Oct 20 21:11:26 CEST 2004


On Wed, Oct 20, 2004 at 04:20:08PM -0200, Sidnei da Silva wrote:
[...]
> | object cache consistent... perhaps sqlos should use that cache, rather than
> | manage its own seperate one?
> 
> It uses that cache... except it has one per thread *wink*. The list of
> objects to be synced is not a cache.

sqlos has one connection per thread, so there's also one SQLObject cache per
thread...

You're right that a cache isn't necessarily holding the same set of objects
as the set that needs to by synced, but at a glance that seems to be true
with SQLObject.  I'd want to do more than glance to be certain, though :)

It feels like unnecessary duplication to have SQLObject and sqlos both
tracking objects independently, but on the other hand relying on SQLObject
internals like that might be a bit fragile.

[...]
> I would make the fix myself, but I prefer to wait for your testcase.

Coming later tonight, I hope :)

-Andrew.




More information about the z3-sqlos mailing list