Re: Improving PL/PgSQL (was: Re: plpgsql defensive mode)

SELECT .. INTO vs. TOO_MANY_ROWS

+1 .. possible every where

Variable assignments

+1 .. only in "defensive mode"

Single-row operations

+1 .. only in "defensive mode" without special syntax

EXECUTE and FOUND

-1 .. it is emulation of PL/SQL behave.. so introduction can do too high unhappy surprise if somebody will migrate to Oracle -- the syntax is too similar 

OUT parameters

-1 .. to proposal .. It is in contradiction with current feature. Next it is nonsense. INTO clause should to contains only plpgsql variables - in 9.x Postgres there is not possible issue.
postgres=# create table x(a int, b int);
CREATE TABLE
postgres=# insert into x values(10,20);
INSERT 0 1
postgres=# create or replace function foo(out a int, out b int)
postgres-# returns record as $$
postgres$# begin
postgres$#   select x.a, x.b from x into a, b;
postgres$#   return;
postgres$# end;
postgres$# $$ language plpgsql;
CREATE FUNCTION
postgres=# select * from foo();
 a  | b 
----+----
 10 | 20
(1 row)

Assertions

-1 to proposed syntax - I wrote about my reasons in other thread.

Regards

Pavel