I'm trying to understand how Django 1.0 handles connections. This is  
from the django docs, on the subject of raw SQL:

     from django.db import connection
     cursor = connection.cursor()
     cursor.execute("select ...")
     row = cursor.fetchone()

If I have a Django app running lots of requests, then how are  
connections handled? Is connection the same in each request, even  
requests running concurrently? That can't possibly be the case,  
(could it)? So does each request get its own? When are connections  
closed? When closed are they really closed, or just returned to a  
pool? Can the pool be configured, (e.g. to set the postgres  
search_path)?

Sorry to ask such basic questions, but I've been unable to find this  
information documented.

Jack Orenstein


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to