| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal: OUT parameters for plpgsql |
| Date: | 2005-03-22 02:03:17 |
| Message-ID: | 3894.1111456997@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:
> I think that not specifying OUT parameters when invoking a function is a
> little of confusing but it gives us a lot: its much easier to develop
> since we don't have to add a stack of infrastructure for host variables,
> for one.
Also, it doesn't stop us from adding that infrastructure later. The
call syntax SELECT * FROM foo(...) will still do what it has been doing
for awhile, but you could imagine inventing other call syntaxes that
accommodate host variables more directly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2005-03-22 03:11:18 | Re: Prevent conflicting SET options from being set |
| Previous Message | Gavin Sherry | 2005-03-22 01:57:45 | Re: Proposal: OUT parameters for plpgsql |