From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "Vianello, Daniel A" <Daniel(dot)Vianello(at)charter(dot)com> |
Cc: | Jay Riddle <jcriddle4(at)yahoo(dot)com>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, john snow <ofbizfanster(at)gmail(dot)com>, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: configure postgtresql to order NULLS FIRST instead of the default NULLS LAST |
Date: | 2019-01-04 15:58:13 |
Message-ID: | CAKFQuwYMa32Gx2Gcj7pMbjDLEkpTCe0VXAsdp+JWLhWA=1mXuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Friday, January 4, 2019, Vianello, Daniel A <Daniel(dot)Vianello(at)charter(dot)com>
wrote:
> Or you could create views to do complex sorting on a table and have users
> use the view instead of the table, but that is still extra development per
> table, not your apparently desired global change of behavior.
>
> Most views should not specify a sort order. Client-sent queries should
append order by according to their need in presenting the data to the
user-side of the system.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Froehlich | 2019-01-14 20:55:27 | pg_upgrade on new boot / Where to mount filesystems for tablespaces / other zfs questions |
Previous Message | Vianello, Daniel A | 2019-01-04 15:44:41 | RE: configure postgtresql to order NULLS FIRST instead of the default NULLS LAST |