Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error

Поиск
Список
Период
Сортировка
От Mor Lehr
Тема Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
Дата
Msg-id CALyvM2b+5ERWeUK5av2udxMzGk18eaUitzrrAAM7h9ZTz=yMRg@mail.gmail.com
обсуждение исходный текст
Ответ на Missing semicolumn in anonymous plpgsql block does not raise syntax error  (Mor Lehr <mor.lehr@deel.com>)
Список pgsql-bugs
Дерево обсуждения
Thanks for not letting this be forgotten :)
Unfortunately, plpgsql_check does not help me because it's not supported on AWS.
I also saw you wrote a patch which is still pending, I will probably have to wait for that.

Thanks again,
Mor

On Thu, Feb 6, 2025 at 7:48 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
Hi

ne 2. 6. 2024 v 18:25 odesílatel Mor Lehr <mor.lehr@deel.com> napsal:
Thanks for the reference.
We learn new stuff every day.

You can close the case.
Thanks, Mor


plpgsql_check can now detect this issue


Regards

Pavel


On Sun, Jun 2, 2024, 18:31 David G. Johnston <david.g.johnston@gmail.com> wrote:
On Sunday, June 2, 2024, Mor Lehr <mor.lehr@deel.com> wrote:
Thanks for the prompt reply.
Can you please refer me to the section in the documentation that describes this behavior?
This (automatically interperting 1 as select 1) is totally an unexpected behavior for me.


“As explained previously, the expression in such a statement is evaluated by means of an SQL SELECT command sent to the main database engine.”

David J.

В списке pgsql-bugs по дате отправления: