| From: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Michael van der Kolff <mvanderkolff(at)gmail(dot)com>, postgre <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Overriding natural order of query results for a subset |
| Date: | 2021-05-29 16:34:23 |
| Message-ID: | Iw_TZN9JOOOQfQg8r_9MQJS3Wd8R5MU8O6zAg0nYziTVJ_XVeXyEvF3nItgN30oljmFNJq5MFdzDwCV9MaD6NIXka0uncdPsz0_ZdazXL2o=@protonmail.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, 29 May 2021 17:06, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 5/29/21 9:00 AM, Laura Smith wrote:
>
> > I did try "nulls last" but will give it another go, maybe I messed up on the ordering of clauses.
>
> Unless the fields you are ordering on contain NULLs I'm not sure how
> this is going to deal with your issue.
>
Reading between the lines of the poster who suggested it, I'm guessing the suggestion was to add an "int" column, most of which is null except for numbers where needed for ordering and then having "order by vip_num_order,order by last_name" in my select clause.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2021-05-29 16:44:14 | Re: Overriding natural order of query results for a subset |
| Previous Message | Adrian Klaver | 2021-05-29 16:25:48 | Re: AWS forcing PG upgrade from v9.6 a disaster |