JP wrote: > Not a dumb question at all. I'll try to explain better by contrasting > how multi-db handles connections with how connections are kept thread > local in trunk.
BTW, I happen to know how it works now since I was among those who was trying to solve threading issues before Eugene Lazutkin's universal patch with DatabaseWrapper inherited from local(). I'm asking because I'm worried if something new could break something working :-) > In multi-db, all connections (including the default that you can access > as django.db.connection) are managed through a LazyConnectionManager > instance, This explains it all, thank you! I now actually found this code in db/backends/__init__.py and from the look of it I agree that inheriting DatabaseWrapper from local() is no longer needed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
