Re: SQLJSON: errmsg(" .. should ...") -> must

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: SQLJSON: errmsg(" .. should ...") -> must
Date: 2025-01-22 06:41:57
Message-ID: CA+HiwqFweeCR3cAY-09KBVWOY8m=sXbSHBRxgfWLve1ga=ZMRQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 21, 2025 at 11:42 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> On 2025-Jan-13, Alvaro Herrera wrote:
>
> > There's a few recent SQL/JSON error messages in which we say something
> > "should" be something else. We avoid this, so I think we shouldn't use
> > it here either.
>
> Pushed.

Sorry Alvaro for not noticing sooner.

I looked at db19a5061ce and it all looks fine to me.

--
Thanks, Amit Langote

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-01-22 06:47:06 Re: Pgoutput not capturing the generated columns
Previous Message jian he 2025-01-22 06:21:05 add function argument name to substring and substr