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

From Amit Langote
Subject Re: remaining sql/json patches
Date
Msg-id CA+HiwqHU7odMsD-c+Un++3W8bRZwS7aT1DUdKwLyH9sHXZKd7Q@mail.gmail.com
Whole thread Raw
In response to Re: remaining sql/json patches  (Nikita Malakhov <hukutoc@gmail.com>)
Responses Re: remaining sql/json patches
List pgsql-hackers
Hi Nikita,

On Thu, Oct 26, 2023 at 2:13 AM Nikita Malakhov <hukutoc@gmail.com> wrote:
> Amit, on previous email, patch #2 - I agree that it is not the best idea to introduce
> new type of logic into the parser, so this logic could be moved to the executor,
> or removed at all. What do you think of these options?

Yes maybe, though I'd first like to have a good answer to why is that
logic necessary at all.  Maybe you think it's better to emit an error
in the SQL/JSON layer of code than in the type input function if it's
unsafe?

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



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Document aggregate functions better w.r.t. ORDER BY
Next
From: David Steele
Date:
Subject: Re: Remove dead code in pg_ctl.c