X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4D187D1C4CA for ; Fri, 8 Aug 2003 04:04:47 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 69399-08 for ; Fri, 8 Aug 2003 01:03:20 -0300 (ADT) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id 7E4A2D1C513 for ; Fri, 8 Aug 2003 01:04:34 -0300 (ADT) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 26124; Thu, 07 Aug 2003 20:25:08 -0700 Message-ID: <3F33205C.6040308@joeconway.com> Date: Thu, 07 Aug 2003 21:00:28 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Berkus Cc: Bruce Momjian , PostgreSQL-development Subject: Re: TODO items References: <200308080201.h78212x26726@candle.pha.pa.us> <200308072036.22437.josh@agliodbs.com> In-Reply-To: <200308072036.22437.josh@agliodbs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/442 X-Sequence-Number: 42100 Josh Berkus wrote: >> o Allow array declarations and other data types in PL/PgSQL DECLARE >> o Allow PL/PgSQL to support array element assignment > > AFAIK, these two are not done, but they are redundant. Either one requires > the implementation of the other. They are done (at least the array declarations and array element assignment part): create or replace function test() returns integer[] as ' declare v_ret integer[] := ''{}''; begin v_ret[1] := 1; v_ret[2] := 2; return v_ret; end; ' language plpgsql; CREATE FUNCTION regression=# select test(); test ------- {1,2} (1 row) >> o Add PL/PgSQL PROCEDURES that can return multiple values > > Hmmm ... I know how this got on the TODO, but it's a fragment of a larger > suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much > sense on its own without the other elements; maybe we should take it off > until I can make a full proposal? Is this somehow different from table functions (SRFs)? >> o Add table function support to pltcl, plperl, plpython > > If this was done, I would dearly love to know about it ... > Pretty much sure this has not been done. I'll be happy to work with someone if they want to pick this up, but I don't use them enough to feel comfortable doing it myself. Joe