Личный кабинет
Укажите e-mail, на который будет выслан код восстановления пароля.
На указанный вами адрес e-mail был выслан код подтверждения аккаунта. Введите полученный код для продолжения:
Введите новый пароль два раза:
"David G. Johnston" <david.g.johnston@gmail.com> writes:On Tue, Jun 7, 2022 at 1:30 PM PG Doc comments form <noreply@postgresql.org>wrote:It looks like INSERT INTO ... RETURNING allows defining a target for thereturned values like SELECT ... INTO does. That isn't how it works. RETURNING simply turns INSERT into a result setproducing SQL Command. And SQL doesn't have a concept of "target"(variables) in the sense you are thinking. pg/pgsql does, allowing resultset data to be placed into variables. Right. And in fact this *is* documented in the context of pl/pgsql: https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-SQL-ONEROW regards, tom lane
On Tue, Jun 7, 2022 at 1:30 PM PG Doc comments form <noreply@postgresql.org>wrote:It looks like INSERT INTO ... RETURNING allows defining a target for thereturned values like SELECT ... INTO does.
It looks like INSERT INTO ... RETURNING allows defining a target for thereturned values like SELECT ... INTO does.
That isn't how it works. RETURNING simply turns INSERT into a result setproducing SQL Command. And SQL doesn't have a concept of "target"(variables) in the sense you are thinking. pg/pgsql does, allowing resultset data to be placed into variables.
В списке pgsql-docs по дате отправления: