| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add json_object(text[], json[])? |
| Date: | 2019-10-24 16:37:30 |
| Message-ID: | CA+renyU3LHWw8NW40nzcB=i4KVRqrjPoJVdB7Rvi-z839wCo-g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 24, 2019 at 8:52 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I think a potential problem is creation of ambiguity where there was
> none before.
I agree that's not nice, and it seems like a new name might be better.
> Also, as the prototype implementation shows, it's not like you
> can't get this functionality today ... you just need to cast
> jsonb to text. Admittedly that's annoying and wasteful.
I don't think that gives the same result, does it? For example:
# select jsonb_object(array['foo'], array['[{"bar-bar": ["baz"]}]'::jsonb]);
jsonb_object
---------------------------------------
{"foo": "[{\"bar-bar\": [\"baz\"]}]"}
You can see the values are JSON strings, not JSON arrays/objects/etc.
Regards,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul A Jungwirth | 2019-10-24 16:46:12 | Re: Add json_object(text[], json[])? |
| Previous Message | Victor Spirin | 2019-10-24 16:11:59 | psql tab-complete |