Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 58695475A93 for ; Wed, 14 Aug 2002 14:30:57 -0400 (EDT) Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com [216.136.174.115]) by postgresql.org (Postfix) with SMTP id 64A02475A52 for ; Wed, 14 Aug 2002 14:30:56 -0400 (EDT) Received: from psc.progress.com (HELO Yahoo.com) (janwieck@192.233.92.200 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 14 Aug 2002 18:30:56 -0000 Message-ID: <3D5AA1DD.B4F6D946@Yahoo.com> Date: Wed, 14 Aug 2002 14:30:53 -0400 From: Jan Wieck X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.2.14-6.1.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Momjian Cc: John Proctor , Neil Conway , josh@agliodbs.com, peter_e@gmx.net, tgl@sss.pgh.pa.us, pgsql-patches@postgresql.org Subject: Re: [SQL] 16 parameter limit References: <200208140243.g7E2hI323252@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/270 X-Sequence-Number: 4806 Bruce Momjian wrote: > > Added to TODO: > > o Improve PL/PgSQL exception handling Exception handling? You're talking about nested transaction support and catchable errors in the first place, and then (a year later) making use of that functionality in the procedural languages, right? > o Allow PL/PgSQL parameters to be specified by name and type during > definition > o Allow PL/PgSQL function parameters to be passed by name, > get_employee_salary(emp_id => 12345, tax_year => 2001) CREATE FUNCTION is in no way PL/pgSQL specific. PL/pgSQL simply works around that lack with the ALIAS syntax in the DECLARE section. > o Add PL/PgSQL packages This really is a 100% PL/PgSQL problem. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #