Re: remaining sql/json patches - Mailing list pgsql-hackers

From Amit Langote
Subject Re: remaining sql/json patches
Date
Msg-id CA+HiwqHCSKqjR=KD5CaecTZNZEaTYg3AZEd4AWBuVi=G1+k9SQ@mail.gmail.com
Whole thread Raw
In response to Re: remaining sql/json patches  (jian he <jian.universality@gmail.com>)
Responses Re: remaining sql/json patches
List pgsql-hackers
On Tue, Aug 15, 2023 at 5:58 PM jian he <jian.universality@gmail.com> wrote:
> 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?

You are correct.

> Also in above quoted second last
> line should be <literal>ON EMPTY</literal> ?

Correct too.

> Other than that, the doc looks good.

Thanks for the review.

I will post a new version after finishing working on a few other
improvements I am working on.

--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_logical_emit_message() misses a XLogFlush()
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: WIP: new system catalog pg_wait_event