Re: [HACKERS] PL/pgSQL - for discussion (RETURN)

From: Zeugswetter Andreas <andreas(dot)zeugswetter(at)telecom(dot)at>
To: "'pgsql-hackers(at)hub(dot)org'" <pgsql-hackers(at)hub(dot)org>
Subject: Re: [HACKERS] PL/pgSQL - for discussion (RETURN)
Date: 1998-03-13 10:12:21
Message-ID: 01BD4E70.E6F10220@pc9358.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Returning from the function
>
> RETURN <expr>;
>
> The function terminates and the value of <expr> will be
> returned to the upper executor. The return value of a
> function cannot be undefined. If control reaches the end
> of the toplevel block of the function without hitting a
> RETURN statement, a runtime error will occur.

1. I think we should allow functions/procedures, that don't have a return value.
(think about a proc that only does an update, why return anything except an error)
2. I think the RETURN will need a WITH RESUME, so a procedure can return more than one row.

create dba procedure "dns".getusers()
returning varchar(16), smallint;
define gotuser varchar(16);
define gotadmin smallint;
execute procedure checkadmin();
foreach select uname, admin into gotuser, gotadmin from passwd
return gotuser, gotadmin with resume;
end foreach;
end procedure;

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Martin 1998-03-13 10:18:04 Re: [HACKERS] varchar() vs char16 performance
Previous Message Zeugswetter Andreas 1998-03-13 10:03:12 Re: [HACKERS] PL/pgSQL - for discussion (ELOG)