Looking back over the multi-db branch today, I realized that it seems to be duplicating the thread locality of connections. The connection management classes in multi-db django.db manage all connections as thread local, and the DatabaseWrapper classes in the backends are all subclasses of local.
I may be missing something, but I think the latter locality can be safely removed in multi-db. DatabaseWrappers don't have to be local because each instance can only be accessed in a particular thread anyway. Since I had previously said multi-db was feature complete, I thought I should bring the change up here before comitting it. Let me know if you have any objections or can see that I am missing something. I'll commit the change within a couple of days if there are no objections, or sooner if anyone wants to try it now. JP --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
