From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200208141834.g7EIYe015655@candle.pha.pa.us>
Subject: Re: [SQL] 16 parameter limit
In-Reply-To: <3D5AA1DD.B4F6D946@Yahoo.com>
To: Jan Wieck <JanWieck@Yahoo.com>
Date: Wed, 14 Aug 2002 14:34:40 -0400 (EDT)
Cc: John Proctor <jproctor@prium.net>,
	Neil Conway <nconway@klamath.dyndns.org>, josh@agliodbs.com,
	peter_e@gmx.net, tgl@sss.pgh.pa.us, pgsql-patches@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Jan Wieck wrote:
> 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?

Uh, I guess.  Not sure.

> 
> >         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.

Text updated to:

        o Allow parameters to be specified by name and type during      
          definition
        o Allow function parameters to be passed by name,
          get_employee_salary(emp_id => 12345, tax_year => 2001)

> >         o Add PL/PgSQL packages
> 
> This really is a 100% PL/PgSQL problem.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073