JP wrote: > 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.
I didn't look how exactly multi-db branch manages connection so my question may be dumb, sorry. If you intend remove the inheritance of DatabaseWrapper from locals does it mean that when using single DB DatabaseWrappers will be shared between threads? > DatabaseWrappers don't have to be local > because each instance can only be accessed in a particular thread > anyway. I don't exactly understand this bit also. Does it mean that each thread gets its own instance or that threads can access some (shared) instance? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
