From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: plpgsql, solution for derivated types of parameters |
Date: | 2010-10-08 13:55:27 |
Message-ID: | 21663.1286546127@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> the current plpgsql syntax doesn't offer a functionality to define
> some variable with type as element of some other array variable or
> reverse order. The primary goal of this proposal is enahancing plpgsql
> for better working with polymorphic types.
I haven't seen any actual field complaints that would be solved by this.
How often is it really going to be useful?
> DECLARE elementvar IS ELEMENT OF arrayvar;
> DECLARE arrayvar IS ARRAY OF varname;
Both of these notations seem pretty inconsistent with the rest of
plpgsql, as well as being dead ends when you think about extensions to
more complex situations like arrays of records or records of arrays.
I'd expect to do the former with something like "arrayvar[0]%type" and
the latter with "var%type[]". Possibly some parentheses would be needed
to make this non-ambiguous.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-08 14:11:58 | Re: Issues with Quorum Commit |
Previous Message | Fujii Masao | 2010-10-08 13:46:49 | Re: Issues with Quorum Commit |