Jean-François wrote: > Oops... I haven't thought to trace connect/disconnect operation to the > database only commit/rollback. > Now, I have a better understanding of the underlaying model. I suspect > that open a database connection then closing it for each request may > be a fairly expensive operation on most database systems, but I have > no bench for this.
Indeed, it's expensive. And Oracle is the champion here, BTW. However it's always recommended to use external connection pooling solutions, like SQLRelay for Oracle, pg_pool for Postgres, etc. They are usually smart enough to do rollback instead of closing and keep an open connection for the following rounds. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
