| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, 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-10-26 02:32:13 |
| Message-ID: | CA+HiwqHU7odMsD-c+Un++3W8bRZwS7aT1DUdKwLyH9sHXZKd7Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Nikita,
On Thu, Oct 26, 2023 at 2:13 AM Nikita Malakhov <hukutoc(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2023-10-26 03:38:33 | Re: Remove dead code in pg_ctl.c |
| Previous Message | David Rowley | 2023-10-26 02:12:56 | Re: Document aggregate functions better w.r.t. ORDER BY |