From: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Questioning an errcode and message in jsonb.c |
Date: | 2023-09-19 07:55:48 |
Message-ID: | CAKU4AWrQ8fTuNx84doWf1ixMwgV3BrTXXrVP5a3FY+3rE4tm2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Thanks for raising this issue in a more public way:)
On Tue, Sep 19, 2023 at 12:55 AM Chapman Flack <chap(at)anastigmatix(dot)net>
wrote:
>
> It would make me happy if the message could be changed, and maybe
> ERRCODE_INVALID_PARAMETER_VALUE also changed, perhaps to one of
> the JSON-specific ones in the 2203x range.
>
I'd agree with this.
> By the same token, the message and the errcode are established
> current behavior, so there can be sound arguments against changing
> them (even though that means weird logic in rewriting the expression).
>
This is not a technology issue, I'd be pretty willing to see what some
more experienced people say about this. I think just documenting the
impatible behavior is an option as well.
--
Best Regards
Andy Fan
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Shinderuk | 2023-09-19 08:06:25 | Re: Fix error handling in be_tls_open_server() |
Previous Message | Ryoga Yoshida | 2023-09-19 07:23:36 | Re: Bug fix for psql's meta-command \ev |