| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Nikita Glukhov <glukhov(dot)n(dot)a(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com> |
| Subject: | Re: SQL:2023 JSON simplified accessor support |
| Date: | 2025-03-27 14:27:50 |
| Message-ID: | c7dc6735-57cb-4287-871f-4c92a7205357@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13/03/2025 15:02, Alexandra Wang wrote:
> Hi Mark,
>
> Thank you so much for reviewing! I have attached the new patches.
>
Hi Alex,
I am reviewing this from a feature perspective and not from a code
perspective. On the whole, this looks good to me from a standards point
of view.
There are two things that stand out to me about this feature:
1) I am not seeing the ** syntax in the standard, so does it need to be
signaled as not supported? Perhaps I am just overlooking something.
2) There is no support for <JSON item method>. Since this appears to be
constructing a jsonpath query, could that not be added to the syntax and
allow jsonpath to throw the error if the function doesn't exist?
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-03-27 14:55:39 | Re: Better HINT message for "unexpected data beyond EOF" |
| Previous Message | Andres Freund | 2025-03-27 14:19:23 | Re: Use CLOCK_MONOTONIC_COARSE for instr_time when available |