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

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: lukas(dot)eder(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
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-02-26 14:20:08
Message-ID: 2abdb464-27f5-4759-bb0b-f09ab5b5ceab@postgresfriends.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 26/02/2026 10:57, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19418
> Logged by: Lukas Eder
> Email address: lukas(dot)eder(at)gmail(dot)com
> PostgreSQL version: 18.2
> Operating system: Linux
> Description:
>
> When using the ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor by query>
> syntax, 6.34 GR 4) b) i) says that empty tables should produce a JSON array
> with no elements (intuitively), not NULL.
>
> Try this:
>
> select json_array(select 1 where false);
>
> It produces NULL, not []

I can confirm that postgres violates the standard here.

--

Vik Fearing

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-02-26 15:54:10 BUG #19419: Cannot create custom functions using python3u
Previous Message Swirl Smog Dowry 2026-02-26 10:18:43 pg_get_viewdef() produces non-round-trippable SQL for views with USING join on mismatched integer types