From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: JSON_TABLE |
Date: | 2022-04-04 22:31:04 |
Message-ID: | 844dcd0e-3f02-ce5d-a319-7787c028d779@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-04-05 02:10:16 | pgsql: Update some tests in 013_crash_restart.pl. |
Previous Message | Erik Rijkers | 2022-04-04 22:16:52 | Re: pgsql: JSON_TABLE |