Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Fearing <vik(at)postgresfriends(dot)org>, lukas(dot)eder(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>
Date: 2026-04-21 05:45:01
Message-ID: CAMbWs4-znpASziLng3MUusSqEd7AVgoiy7jF7+oVLZx8_1euJw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Apr 21, 2026 at 12:57 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> On Tue, Apr 21, 2026 at 9:57 AM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> > (maybe we should place the multi-line comment above the field.)

> Makes sense. Perhaps we should also move the description of individual
> fields, where needed, into the comment above the struct definition
> like it is done for the nearby JsonValueExpr. Like this:

This looks even better. I will take this approach. Thanks!

- Richard

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message François Jehl 2026-04-21 07:40:47 Re: BUG #19460: FULL JOIN rewriting issue on empty queries
Previous Message Amit Langote 2026-04-21 03:57:12 Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>