| From: | solai v <solai(dot)cdac(at)gmail(dot)com> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: extend JSON_TABLE top level path expression |
| Date: | 2026-06-11 10:31:36 |
| Message-ID: | CAF0whueGZAf5-mUP5byJAYWgSuuT6gPnfSoy1sb3tCzHiD86yg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Jian,
I reviewed and tested patch v2 .
Before applying the patch JSON_TABLE accepted only literal top-level
patch string such as '$.a' and rejected equivalent path expression
such as '$'||.'a' with:
ERROR :only string constants are supported in JSON_TABLE path specification
After applying the patch ,JSON_TABLE correctly accepts path
expressions and returns the expected results.
I verified cases using string concatenation (e.g. '$' || '.a' and '$'
|| '.' || 'a'),,while existing behavior with literal path strings
remained unchanged.
I also confirmed that JSON_QUERY already accepts such patch
expressions,so the patch makes JSON_TABLE behavior more consistent
with other SQL/JSON functions.
The patch applied successfully and tested queries behaved as expected.
Thanks for working on this improvement.
Regards
Solai
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-06-11 10:34:13 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Ewan Young | 2026-06-11 09:59:55 | Re: Make SPI_prepare argtypes argument const |