Re: Proposal: OUT parameters for plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: OUT parameters for plpgsql
Date: 2005-03-22 01:29:59
Message-ID: 3593.1111454999@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> (When there is just one, should the default be to return that type
>>> rather than a one-column RECORD?)

> ANSI SQL allows at most one OUT parameter for a function (which can be
> used instead of having the function return a value via the usual means).

OK, so that answers my question above: a single OUT parameter should be
equated to an ordinary return value, not a RECORD, so as to emulate this
aspect of the spec.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-03-22 01:36:39 Re: Proposal: OUT parameters for plpgsql
Previous Message Tom Lane 2005-03-21 23:15:51 Re: Proposal: OUT parameters for plpgsql