Re: Implementing postgres database timeouts

On Wed, Feb 4, 2009 at 1:41 PM, RahulDave wrote: > > The Plot thickens a bit with whats happening in the case of the eaten > up QueryCanceled Error. Basically, > somewhere in the list protocol, the QueryCancelledError thrown by > psycopg2 gets eaten up! > > [snip details] > I'm delving into the i

Re: Implementing postgres database timeouts

The Plot thickens a bit with whats happening in the case of the eaten up QueryCanceled Error. Basically, somewhere in the list protocol, the QueryCancelledError thrown by psycopg2 gets eaten up! Here's what I did(django 1.0), in django/db/models/query.py 143 def __repr__(self): 144 i

#9638 - app_label in related_name

Is it possible to apply http://code.djangoproject.com/ticket/9638? I'm using using a "Very Ugly Hack"(TM) to get this behaviour, but it would be really nice to kill it. Thanks. -- ()_() | That said, I didn't actually _test_ my patch. | + (o.o) | That's what users are for!