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

Hi

ne 2. 6. 2024 v 18:25 odesílatel Mor Lehr <mor(dot)lehr(at)deel(dot)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

https://okbob.blogspot.com/2025/02/plpgsqlcheck-raise-warning-when-syntax.html

Regards

Pavel

> On Sun, Jun 2, 2024, 18:31 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> wrote:
>
>> On Sunday, June 2, 2024, Mor Lehr <mor(dot)lehr(at)deel(dot)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.
>>>
>>
>>
>> https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-ASSIGNMENT
>>
>> “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.
>>
>>