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
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
On Tue, 2009-02-03 at 07:03 -0800, RahulDave wrote:
> Thanks for the reply!
>
> On Feb 3, 1:25 am, Malcolm Tredinnick
> wrote:
>
> >
> > > My first question is , how could I wrap eachdjangoquery in such a
> > > set of stataemtns. I could figure that its the web ui from a custom
> > > header
Thanks for the reply!
On Feb 3, 1:25 am, Malcolm Tredinnick
wrote:
>
> > My first question is , how could I wrap eachdjangoquery in such a
> > set of stataemtns. I could figure that its the web ui from a custom
> > header or user agent and set this , but its not something I could juck
> > o
On Mon, 2009-02-02 at 10:16 -0800, RahulDave wrote:
> Hi Folks,
> I have a django astronomy application which fronts a 73 million row
> main table and 150 million row secondary table database, highly
> indexed of-course. The back-end database is postgres. The application
> itself is two-fold, a we
Thought I should perhaps be more illustrative of the problem.
At django shell:
--
In [2]: from lcdb.maindb.models import LCOT
In [3]: from lcdb.maindb.models import Snippet
In [4]: bset=LCOT.objects.all()
In [5]: bset
Out[5]: []
In [6]:
meanwhile at postgres logs:
LOG:
Hi Folks,
I have a django astronomy application which fronts a 73 million row
main table and 150 million row secondary table database, highly
indexed of-course. The back-end database is postgres. The application
itself is two-fold, a web services backend which can tolerate
extremely long queries a
