Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 29 May 2021 17:55, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Michael Nolan htfoot@xxxxxxxxx writes: > > > You probably need some kind order by case when .... else .... end clause, > > where the else clause deals with the non-VIPs, probably negating the need > > for a nulls last clause. > > The idiomatic way to do this, assuming that you create an "is_vip bool" > field or some other way to identify VIPs accurately, is > > ORDER BY is_vip DESC, last_name, first_name > > relying on the fact that bool TRUE > bool FALSE. > > regards, tom lane Thanks tom ! I think yours combined with Adrian's "DEFAULT of 0" is likely to be the winner. Doing some experimenting, it gives me three options: - Leave field as default = default name alphabetic - Add VIPs with same integer = VIPs at the top, ordered alphabetically - Add VIPs with differing integers = VIPs ordered by protocol Thanks all.
