| From: | Erik Rijkers <er(at)xs4all(dot)nl> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: JSON_TABLE |
| Date: | 2022-04-04 22:16:52 |
| Message-ID: | bd76a661-51eb-6bc2-a2c2-cf226017093a@xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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).
Thanks,
Erik Rijkers
| Attachment | Content-Type | Size |
|---|---|---|
| bugmaybe.sh | application/x-shellscript | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2022-04-04 22:31:04 | Re: pgsql: JSON_TABLE |
| Previous Message | Andres Freund | 2022-04-04 21:33:55 | pgsql: dshash: revise sequential scan support. |