From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TABLE-function patch vs plpgsql |
Date: | 2008-07-18 06:01:06 |
Message-ID: | 162867790807172301t12328449m98c541579d47b882@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/7/18 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
>> Maybe we can use some well defined implicit record, maybe NEW (or
>> RESULT, ROW_RESULT, ROW, TABLE_ROW, ...) like trigger - some like
>
> That sounds like exactly the sort of kluge-solution that I didn't
> want to get involved with ...
>
> Anyway, the core feature is in, and we still have several months
> before 8.4 feature freeze to debate how plpgsql ought to interact
> with it.
>
I agree.
Regards
p.s.
other solution - using referenced types
declare foorec fcename%ROWTYPE -- allows only current fce name
fooscalar fcename.col%TYPE
regards
Pavel Stehule
and many thanks for commit this patch
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2008-07-18 06:23:43 | Re: Load spikes on 8.1.11 |
Previous Message | Tom Lane | 2008-07-18 05:37:10 | Re: [PATCH]-hash index improving |