On Mon, Feb 18, 2013 at 2:21 PM, Carl Meyer <c...@oddbird.net> wrote:
> On 02/18/2013 12:17 PM, Michael wrote: > > On Mon, Feb 18, 2013 at 2:03 PM, Jacob Kaplan-Moss <ja...@jacobian.org > > <mailto:ja...@jacobian.org>> wrote: > > > > On Mon, Feb 18, 2013 at 1:51 PM, Michael <newmani...@gmail.com > > <mailto:newmani...@gmail.com>> wrote: > > > I will argue, however, that the AWS use case is a reason we need > > this to be > > > an OPTION, not automatic. > > > > Check out Aymeric's patch; it is indeed an option triggered by > > DATABASES[CONN_MAX_AGE]. > > > > > > Unless I am reading it wrong, only on the next database query. So if I > > set the connection to 0 and don't have a connection to the database > > after the validation on start, the connections still are sleeping. I > > really never want to hang onto a DB connection. > > No, it's not on the next DB query, it's at the request_finished signal > (which is the same point when Django will currently close your > connection for you). So the effect with CONN_MAX_AGE=0 is really not > distinguishable from what you get currently. > > Carl > > Thanks, Carl, I had missed that. Then I have no objection. I will still take a deeper dive this week, let you know how it goes. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
