Re: [SQLObject] bug: connection/transaction leak?

[Guenther S. <gs...@sy...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 19 December 2003 22:05, Ian Bicking wrote:

hi,

> Each new Account is going to have a reference to the connection, so
> that's to be expected.  Hmm... and the accounts won't be deleted
> because they are cached.  That's the problem, then.  Maybe the
> transaction simply needs to clear its cache on a commit/rollback (well,
> you can't really clear the cache, but you can make all the objects
> GCable).

hmm..  shouldn't objects in the cache automatically expire 'faster' when i =
set=20
the cullFrequency to a lower value? i tried setting the cullFrequency to 5=
=20
and running gc.collect() after every iteration, but the refcount to the=20
connection still stays the same (resp. +1 at every iteration).

on the other hand when i disable caching by passing "cache =3D False" to th=
e=20
connection & run the gc it works fine (the refcount to 'conn' doesn't=20
increase).

cu
/gst

=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/5GWeZtF7I/+gjcERAva+AJ9H/M2TjDu4GeP+ypEreDrud/zOVQCgiNdp
hZ13/zMOlWTM+0/bkJzXYHA=3D
=3D3rEe
=2D----END PGP SIGNATURE-----