Re: SQL/JSON features for v15 - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: SQL/JSON features for v15
Date
Msg-id abd31e0b-56aa-044f-6700-8a1c1bba87f1@dunslane.net
Whole thread Raw
In response to Re: SQL/JSON features for v15  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: SQL/JSON features for v15
List pgsql-hackers
On 2022-08-31 We 07:01, Amit Langote wrote:
> On Wed, Aug 31, 2022 at 3:51 PM Amit Langote <amitlangote09@gmail.com> wrote:
>>  SELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING int DEFAULT 111 ON ERROR);
>> - json_value
>> -------------
>> -        111
>> -(1 row)
>> -
>> +ERROR:  syntax error at or near "DEFAULT"
>> +LINE 1: ...ELECT JSON_VALUE(jsonb '"aaa"', '$' RETURNING int DEFAULT 11...
>>
>> Is it intentional that you left many instances of the regression test
>> output changes like the above?
> Actually, thinking more about this, I am wondering if we should not
> remove the DEFAULT expression productions in gram.y.  Maybe we can
> keep the syntax and give an unsupported error during parse-analysis,
> like the last version of the patch did for DEFAULT ON EMPTY.  Which
> also means to also leave JsonBehavior alone but with default_expr
> always NULL for now.
>

Producing an error in the parse analysis phase seems best to me.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: plpgsql-trigger.html: Format TG_ variables as table (patch)
Next
From: Robert Haas
Date:
Subject: allowing for control over SET ROLE