Le 17 févr. 2013 à 09:24, James Bennett <[email protected]> a écrit :
> Also, generally we've been a bit wary of doing any kind of DB pooling > at this level in the stack... In this case, the pooler is provided by the cx_Oracle module -- and possibly by the underlying Oracle library. That's different from implementing our own. On an old thread about connection pooling, Malcolm says: "Why wouldn't a backend that talks correctly to pgpool and whatever the equivalent is for MySQL be the right solution?". The ticket discussed here proposes the equivalent for Oracle. The patch looks fairly reasonable. (The style cleanups make it look larger than it is; it's a good idea to omit them in patches intended for review.) It still needs tests, and specifically, tests with multiple databases (per comment 14). I'll send a more general email about connection pooling shortly :) -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
