Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: mirabilos <tg(at)evolvis(dot)org>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
Date: 2023-02-28 00:44:47
Message-ID: CAKFQuwZHTBSz-ELu0Qrdv0tuAUh3B7pFnvAVKnGnUjvj0U33fQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Feb 27, 2023 at 5:22 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

>
> Lastly, if you do need to care about normalizing the output of JSON you
> should consider writing a function that takes arbitrary json input and
> reformats it, rather than trying to build up json from scratch where every
> individual component needs to be aware and take action. i.e., get rid of
> the ORDER BY also. Maybe this belongs in an application layer with tooling
> that already provides this capability.
>
>
Just to clarify/correct myself - if building up json arrays you'll just
remove the distinct and then do a normal aggregate order by based upon
whatever ordering the base data presents. I was thinking you were doing
order by to get keys in order (i.e., jsonb_object_agg) but that isn't the
case here.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jan Bilek 2023-02-28 00:55:02 Re: ERROR: unsupported Unicode escape sequence - in JSON-type column
Previous Message David G. Johnston 2023-02-28 00:22:46 Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)