Re: remaining sql/json patches

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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-11-17 09:17:22
Message-ID: CA+HiwqHbdwAFJ+D7mnnf=MC4Rwj620DE4Lh8X2zLRcirL36jvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 17, 2023 at 4:27 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
> hi.
> minor issues.

Thanks for checking.

> In transformJsonFuncExpr(ParseState *pstate, JsonFuncExpr *func)
> func.behavior->on_empty->location and
> func.behavior->on_error->location are correct.
> but in ExecInitJsonExpr, jsestate->jsexpr->on_empty->location is -1,
> jsestate->jsexpr->on_error->location is -1.
> Maybe we can preserve these on_empty, on_error token locations in
> transformJsonBehavior.

Sure.

> some enum declaration, ending element need an extra comma?

Didn't know about the convention to have that comma, but I can see it
is present in most enum definitions.

Changed all enums that the patch adds to conform.

> + /*
> + * ExecEvalJsonExprPath() will set this to the address of the step to
> + * use to coerce the result of JsonPath* evaluation to the RETURNING
> + * type. Also see the description of possible step addresses this
> + * could be set to in the definition of JsonExprState.ZZ
> + */
>
> "ZZ", typo?

Indeed.

Will include the fixes in the next version.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-11-17 09:40:38 Re: remaining sql/json patches
Previous Message Andrei Zubkov 2023-11-17 08:40:19 Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements