Ivan Sagalaev wrote: > > Though it mandates opening new connection for each request which would > kill even "hello world" if it happens to use Oracle for backend :-). > However this problem is better solved with some external connection pool > solution.
I am all up for a generic connection pool but it is a separate issue. For now I want to resolve multithreading problems. After our talk at PyCon I have some things on my plate to take care first. After that I may come back and do the pool or somebody else may propose a patch, which does exactly that. > I think you should also do this for every backend the same way you did > for Postgres. The problem is not backend specific: if one thread says > connection.close() while the other is doing something with it then the > whole thing will certainly blow under any backend :-). I'll update the patch to include other backends. Thanks, Eugene --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
