Re: remaining sql/json patches

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remaining sql/json patches
Date: 2023-08-15 08:58:01
Message-ID: CACJufxGW+L+FSDgpuYdM-YQb0u+EpESYGtv_xmK1emGDPMvxQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi.
in v11, json_query:
+ The returned <replaceable>data_type</replaceable> has the
same semantics
+ as for constructor functions like <function>json_objectagg</function>;
+ the default returned type is <type>text</type>.
+ The <literal>ON EMPTY</literal> clause specifies the behavior if the
+ <replaceable>path_expression</replaceable> yields no value at all; the
+ default when <literal>ON ERROR</literal> is not specified is
to return a
+ null value.

the default returned type is jsonb? Also in above quoted second last
line should be <literal>ON EMPTY</literal> ?
Other than that, the doc looks good.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Muneeb Anwar 2023-08-15 09:18:29 Generating memory trace from Postgres backend process
Previous Message Dilip Kumar 2023-08-15 08:53:43 Re: New WAL record to detect the checkpoint redo location