From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | emkxp01(at)mtcc(dot)demon(dot)co(dot)uk, hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Re: consttraints.source |
Date: | 1998-01-07 01:36:20 |
Message-ID: | 34B2DC14.B31336F@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I'm seeing similar problems, mainly due to failure to sort correctly
> > even though there is an "order by" clause.
> >
> > I did a few tests and found that the sort sort seemed to fail when there
> > were multiple columns in the "order by" clause. (Not conclusive)
>
> This is a huge help. I think I have found it. I just overhauled the
> readfunc/outfunc code, so it was now very clear that was in the
> Query.sortClause.
>
> Your hint that the it fails when there is more than one sort identifier
> was the trick.
Ah, Keith beat me to the test :) fwiw, the problem was introduced between 971227
and 980101...
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-01-07 02:02:54 | Re: [HACKERS] PostODBC... |
Previous Message | Thomas G. Lockhart | 1998-01-07 01:25:47 | Re: [HACKERS] Postgres acl (fwd) |