pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Oleg Bartunov <obartunov@postgrespro.ru>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: JSON_TABLE
Date: Tue, 5 Apr 2022 15:35:58 -0400
Message-ID: <29db47b6-1193-c568-245e-511247324d86@dunslane.net> (raw)
In-Reply-To: <CAF4Au4zLuht8jAJDxFfji96dKhhcoUwUgPEjsKRqST1gfD=egQ@mail.gmail.com>
References: <E1nbTEj-000KY7-B7@gemulon.postgresql.org>
	<bd76a661-51eb-6bc2-a2c2-cf226017093a@xs4all.nl>
	<844dcd0e-3f02-ce5d-a319-7787c028d779@dunslane.net>
	<CAF4Au4zLuht8jAJDxFfji96dKhhcoUwUgPEjsKRqST1gfD=egQ@mail.gmail.com>


On 4/5/22 15:05, Oleg Bartunov wrote:
> On Tue, Apr 5, 2022 at 1:31 AM Andrew Dunstan <andrew@dunslane.net> wrote:
>>
>> On 4/4/22 18:16, Erik Rijkers wrote:
>>> Op 04-04-2022 om 22:23 schreef Andrew Dunstan:
>>>> JSON_TABLE
>>> Great that this is now committed!
>>>
>>> I notice one changed item: the NESTED-PATH-phrase does not accept an
>>> alias anymore.  The JSON_PATH v59 patches still had:
>>>
>>> | NESTED PATH json_path_specification [ AS path_name ]
>>>   COLUMNS ( json_table_column [, ...] )
>>>
>>> My complaint is only half-hearted because I don't really understand
>>> what the use of such nested-path aliases are.  But it's a change from
>>> the earlier patch, and the nested-path aliases are used too in the
>>> 2017-03 'Technical report ISO/IEC TR 19075-6', which is as near I have
>>> to a SQL Standard description.
>>>
>>> FWIW, I attach example sql+data from that .pdf from ISO (which is not
>>> online anymore).
>>>
>>>
>> These commits are being staggered. The last code patches will be
>> committed tomorrow.
> as for PostgreSQL 15devel-master/fadb48b00e aliases AS works
>
> SELECT
>   jt.*
> FROM
>   house,
>   JSON_TABLE(js, '$.floor[*]'  AS lvl COLUMNS (
>     level int,
>     NESTED PATH '$.apt[*] ? (@.area > 1000)' AS big COLUMNS (
>       no int
>     )
>   ) PLAN (lvl OUTER big) ) jt;
>  level |   no
> -------+--------
>      1 | (null)
>      2 | (null)
> (2 rows)



Yeah, and I think that's the answer to Erik's question about why we need
it, it's so you have a name you can refer to in the PLAN clause, as in
you example.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com






view thread (6+ messages)

Message-ID: <29db47b6-1193-c568-245e-511247324d86@dunslane.net>
Permalink:  ../29db47b6-1193-c568-245e-511247324d86@dunslane.net/
Also on:    postgresql.org/message-id/29db47b6-1193-c568-245e-511247324d86@dunslane.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: andrew@dunslane.net, obartunov@postgrespro.ru, er@xs4all.nl
  Subject: Re: pgsql: JSON_TABLE
  In-Reply-To: <29db47b6-1193-c568-245e-511247324d86@dunslane.net>
  References: <E1nbTEj-000KY7-B7@gemulon.postgresql.org> <bd76a661-51eb-6bc2-a2c2-cf226017093a@xs4all.nl> <844dcd0e-3f02-ce5d-a319-7787c028d779@dunslane.net> <CAF4Au4zLuht8jAJDxFfji96dKhhcoUwUgPEjsKRqST1gfD=egQ@mail.gmail.com> <29db47b6-1193-c568-245e-511247324d86@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox