Re: SQL:2023 JSON simplified accessor support
От | Jelte Fennema-Nio |
---|---|
Тема | Re: SQL:2023 JSON simplified accessor support |
Дата | |
Msg-id | CAGECzQRzrW1+R8LnMJVGgo+SxBjrFBkTy6ajbV2gGE-+p4w1Ag@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: SQL:2023 JSON simplified accessor support (Alexandra Wang <alexandra.wang.oss@gmail.com>) |
Список | pgsql-hackers |
On Thu, 13 Mar 2025 at 15:02, Alexandra Wang <alexandra.wang.oss@gmail.com> wrote: > I have attached the new patches. Okay I finally found the time to look at this. I created a draft PR for pg_duckdb[1] to see if I would run into issues. There was only one real issue I found by doing this. The .* syntax is encoded as NULL in refupperindexpr, but that is currently already a valid representation of a slice operation without specifying upper or lower. The easiest way to reproduce the problem is: CREATE TABLE arr(a int[]); explain (verbose) SELECT a[:] FROM arr; QUERY PLAN ─────────────────────────────────────────────────────────────── Seq Scan on public.arr (cost=0.00..23.60 rows=1360 width=32) Output: a.* That last line should instead be Output: a[:] So I think we need to add a new Star node type, that represents the * literal after parsing. I haven't looked too closely at the code yet.
В списке pgsql-hackers по дате отправления: