Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
Date
Msg-id CAKFQuwaSrWcvZTWEMfzTRLTKkhVJMCqS1Ebibk7U6QRQJPLa3w@mail.gmail.com
Whole thread Raw
In response to Missing semicolumn in anonymous plpgsql block does not raise syntax error  (Mor Lehr <mor.lehr@deel.com>)
Responses Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
List pgsql-bugs
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 by date:

Previous
From: Mor Lehr
Date:
Subject: Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error
Next
From: Mor Lehr
Date:
Subject: Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error