On Mar 2, 2010, at 7:05 PM, vijaya ragavan wrote:
http://code.djangoproject.com/ticket/1237
That ticket is solving a different problem: Multiple threads using the
same connection incorrectly. It was superseded by:
http://code.djangoproject.com/ticket/1442
Which was applied and closed, from a quick examination.
But neither of these tickets are about a connection pool in the sense
that you mean. Django does not have a built-in connection pool. The
typical solution in the PostgreSQL world is to use connection pooling
middleware; I'm not sure what the appropriate equivalent would be for
MSSQL.
--
-- Christophe Pettus
x...@thebuild.com
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
