2010/10/8 Tom Lane <t...@sss.pgh.pa.us>: > Pavel Stehule <pavel.steh...@gmail.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
uff "arrayvar[0]%type" should be in plpgsql spirit? There is nothing similar in Ada, PL/SQL or languages similar to modula. I don't see why my proposal cannot work with more complex types. This is maybe C construct - it must not be used for plpgsql - subscripts can start with other number than zero. DECLARE arrayvar IS ARRAY OF sometype or DECLARE arrayvar IS ARRAY OF somevar%type; possible DECLARE arrayvar IS ARRAY OF somerec.field%type; This syntax is similar to Ada language. > the latter with "var%type[]". Possibly some parentheses would be needed > to make this non-ambiguous. > > regards, tom lane > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
