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.
Agreed! I figured my "clear the cache at the beginning and end of
every request" was sure to work. But it didn't. It *could* be
something weird with transactions, but I am not positive about that.
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?
That is, essentially, correct. This issue arises when using the flup
forking WSGI server. It seems that changes don't quite "stick"
properly. I will make a change to an object in one request, and it
won't seem to "stick" when I make the next request (like the object
is still in the cache in a separate pre-forked process). Its
seemingly random. Sometimes it happens, other times it doesn't!
-- Jonathan
