MIME-Version: 1.0
References: 
 <CAOC+FBU_qEQJxyw03ag_5jryAjB+43frFLveivx3uH=uNo--1w@mail.gmail.com>
 <20210126135238.GA20826@alvherre.pgsql>
 <CAOC+FBUobjupfTb9BKctomaygUf6_24AZo0QHQ2g2e1GaGL7tQ@mail.gmail.com>
 <2338155.1611697339@sss.pgh.pa.us>
In-Reply-To: <2338155.1611697339@sss.pgh.pa.us>
From: Wells Oliver <wells.oliver@gmail.com>
Date: Tue, 26 Jan 2021 22:39:35 -0800
Message-ID: 
 <CAOC+FBVkTvWHumTdrOC0XBiYZ73NPV760u7+fQ+O2iD7ik6OwA@mail.gmail.com>
Subject: Re: json_build_object, numeric types,
 and function limits on 100 arguments
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 pgsql-admin <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000fb13eb05b9dc0ad8"
Precedence: bulk

--000000000000fb13eb05b9dc0ad8
Content-Type: text/plain; charset="UTF-8"

Thanks, Tom. Doing something like:

with t as ( select somekey, someotherkey from mytable ) select
json_agg(t)->0 from t;

Feels a lot more, errr, natural. Would rather have the object than an array
of 1 containing the object, thus the ->0 but this works well and feels
SQL-ish indeed.


On Tue, Jan 26, 2021 at 1:42 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Wells Oliver <wells.oliver@gmail.com> writes:
> > Yeah, thanks, I thought about that: concatenating a few different objects
> > to make a bigger object. Seemed silly, but if there's not a cleaner
> > solution, it does work.
>
> A more SQL-ish way to deal with this might be to use jsonb_agg()
> or jsonb_object_agg().
>
>                         regards, tom lane
>


-- 
Wells Oliver
wells.oliver@gmail.com <wellsoliver@gmail.com>

--000000000000fb13eb05b9dc0ad8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, Tom. Doing something like:<div><br></div><div>with=
 t as ( select somekey, someotherkey from mytable ) select json_agg(t)-&gt;=
0 from t;</div><div><br></div><div>Feels a lot more, errr, natural. Would r=
ather=C2=A0have=C2=A0the object than an array of 1 containing the object, t=
hus the -&gt;0 but this works well and feels SQL-ish indeed.</div><div><br>=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Tue, Jan 26, 2021 at 1:42 PM Tom Lane &lt;<a href=3D"mailto:tgl@ss=
s.pgh.pa.us" target=3D"_blank">tgl@sss.pgh.pa.us</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">Wells Oliver &lt;<a href=3D=
"mailto:wells.oliver@gmail.com" target=3D"_blank">wells.oliver@gmail.com</a=
>&gt; writes:<br>
&gt; Yeah, thanks, I thought about that: concatenating a few different obje=
cts<br>
&gt; to make a bigger object. Seemed silly, but if there&#39;s not a cleane=
r<br>
&gt; solution, it does work.<br>
<br>
A more SQL-ish way to deal with this might be to use jsonb_agg()<br>
or jsonb_object_agg().<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 regards, tom lane<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
><div dir=3D"ltr"><div>Wells Oliver<br><a href=3D"mailto:wellsoliver@gmail.=
com" target=3D"_blank">wells.oliver@gmail.com</a></div></div></div>

--000000000000fb13eb05b9dc0ad8--