It might be good to see what our friends at TurboGears are up to with
http://cheeseshop.python.org/pypi/TGWebServices/
cheers,
peter
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to
Ok, it turns out that when you kick of a thread and use the db a new
database session is created. You do need to explicitly do a
connection.close() at the end of your thread's run method or the
session leaks.
I got rid of all the setDaemon() calls, no good or bad effects.
Cheers,
Peter
--~--
We have an application that has a django front end and a bunch of
backend stuff that uses django's excellent database api.
We've developed using sqlite and recently switched to the postgres back
end.
We leak database sessions and eventually run out of postgres's 100
sessions after several hours
3 matches
Mail list logo
