| From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> |
| Cc: | neilc(at)samurai(dot)com, pgsql-hackers(at)postgresql(dot)org, andrew(at)dunslane(dot)net, tgl(at)sss(dot)pgh(dot)pa(dot)us, josh(at)agliodbs(dot)com |
| Subject: | Re: RETURN QUERY in PL/PgSQL? |
| Date: | 2007-05-04 07:53:43 |
| Message-ID: | e51f66da0705040053t2fa40c2et745106a162251a2d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/25/07, Pavel Stehule <pavel(dot)stehule(at)hotmail(dot)com> wrote:
> for me RETURNS TABLE (a,b) isn't equialent for (OUT a, OUT b) RETURNS SETOF
> RECORD, but
> it's eq. for RETURNS SETOF RECORD ... and SELECT FROM foo() AS (a, b).
>
> Reason:
>
> example: I have table with attr. cust_id, and I want to use parametrized
> view (table function) where I want to have attr cust_id on output.
You can use table aliases to avoid conflicts. (t.cust_id)
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-05-04 08:01:07 | Re: pgsql: Teach tuplesort.c about "top N" sorting, in which only the first |
| Previous Message | Pavel Stehule | 2007-05-04 07:43:00 | Re: RETURN QUERY in PL/PgSQL? |