Kevin Dangoor wrote: > On 11/12/05, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > >>I think someone with a bit more SQLObject knowledge should probably >>take a look at this problem, and see if they can get it fixed. Not >>being able to run in any multi-process environment seems to be a big >>issue, at least to me. > > > Usually, a multiprocess environment should make things easier. > > So, to summarize the problem, when running with SQLObject in a > multiprocess environment, you have been seeing things winding up in > the cache and not leaving it at a request boundary no matter what you > do. > > Is that correct?
I've added two new methods: MyClass.sqlmeta.expireAll() connection.expireAll() The first expires that particular class, the second expires everything for that connection. I'm not 100% sure how this works with transactions, but transactions should be transient (certainly across request boundaries) so I think it should be okay. Anyway, unlike clearing the cache, this expires all objects that can't be garbage collected, so that no lingering objects will be left behind. I'm not sure what the source of problems is, but at least some potential problems should be resolved with this. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
