From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumnus(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: Recent updates |
Date: | 1998-07-15 17:04:21 |
Message-ID: | 199807151704.NAA13760@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > > What does 'select null order by 1;' do now?
> > you can do a NULL test there and prevent oper() from even being
> > called.
>
> postgres=> select null order by 1;
> ?column?
> --------
>
> (1 row)
>
> There are three or four cases in transformSortClause() and I had fixed
> only one case for UNION. A second case is now fixed, in the same way; I
> assigned INT4OID to the column type for the "won't actually happen"
> sort. Didn't want to skip the code entirely, since the backend needs to
> _try_ a sort to get the NULLs right. I'm not certain under what
> circumstances the other cases are invoked; will try some more testing...
>
> Off to work now :)
Good. Yes, I agree we need to put something in that place.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-07-15 17:06:42 | Re: Recent updates |
Previous Message | Andreas Zeugswetter | 1998-07-15 16:39:09 | AW: [HACKERS] "internal error" triggered by EXISTS() |