Re: minor cleanup in plpgsql.sgml
От | Peter Eisentraut |
---|---|
Тема | Re: minor cleanup in plpgsql.sgml |
Дата | |
Msg-id | Pine.LNX.4.44.0311252022350.11097-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: minor cleanup in plpgsql.sgml (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: minor cleanup in plpgsql.sgml
Re: minor cleanup in plpgsql.sgml |
Список | pgsql-patches |
Tom Lane writes: > Robert Treat <xzilla@users.sourceforge.net> writes: > > ! SELECT INTO users_rec * FROM users WHERE user_id=3; > > --- 986,993 ---- > > ! SELECT * FROM users WHERE user_id=3 INTO users_rec; > > Why do you want to change the example to disagree with the advice given > just above? > > : At present, the INTO clause can appear almost anywhere in the SELECT > : statement, but it is recommended to place it immediately after the > : SELECT key word as depicted above. Future versions of PL/pgSQL may be > : less forgiving about placement of the INTO clause. Well, that position is a strange choice. The standard syntax of SELECT INTO in embedded SQL is SELECT a, b, c INTO :x, :y, :z FROM ... This should probably be consistent. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-patches по дате отправления: