Thanks for the reference.We learn new stuff every day.You can close the case.Thanks, Mor
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. 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.
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. 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.
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.
SELECT
pgsql-bugs by date:
Соглашаюсь с условиями обработки персональных данных
