| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Mor Lehr <mor(dot)lehr(at)deel(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error |
| Date: | 2024-06-02 15:31:42 |
| Message-ID: | CAKFQuwaSrWcvZTWEMfzTRLTKkhVJMCqS1Ebibk7U6QRQJPLa3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
>
/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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mor Lehr | 2024-06-02 15:42:38 | Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error |
| Previous Message | Mor Lehr | 2024-06-02 15:26:41 | Re: Missing semicolumn in anonymous plpgsql block does not raise syntax error |