| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | hackers(at)postgreSQL(dot)org (PostgreSQL-development) |
| Subject: | [QUESTIONS] ORDER BY and nulls (fwd) |
| Date: | 1998-01-11 21:43:01 |
| Message-ID: | 199801112143.QAA12845@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Is this fixed yet?
Forwarded message:
> I seem to recall that someone here said that because of the way comparisons
> are done, in an ORDER-BY query, the NULLs will always come up last.
>
> It seems to have another effect, too: if I do a SELECT ... ORDER BY
> col1,col2 - and the col1 attribute has nulls, the rows with the nulls don't
> get sorted at all.
>
> Apparently, this is because the rows which have NULL in the col1 attribute
> are not considered to have an equal value in col1, which is the requirement
> for sorting on col2 - or am I missing something here?
>
> Herouth
>
>
>
>
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-01-11 21:53:27 | Re: New pg_pwd patch and stuff |
| Previous Message | Bruce Momjian | 1998-01-11 21:39:09 | [BUGS] NOTICE:AbortTransaction and not in in-progress state (fwd) |