Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!) - Mailing list pgsql-general

From David G. Johnston
Subject Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
Date
Msg-id CAKFQuwZHTBSz-ELu0Qrdv0tuAUh3B7pFnvAVKnGnUjvj0U33fQ@mail.gmail.com
Whole thread Raw
In response to Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On Mon, Feb 27, 2023 at 5:22 PM David G. Johnston <david.g.johnston@gmail.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.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
Next
From: Jan Bilek
Date:
Subject: Re: ERROR: unsupported Unicode escape sequence - in JSON-type column