Does this complete this TODO?
o Allow parameters to be specified by name and type during
definition
---------------------------------------------------------------------------
Tom Lane wrote:
> CVSROOT: /cvsroot
> Module name: pgsql-server
> Changes by: tgl@svr1.postgresql.org 04/01/06 19:55:19
>
> Modified files:
> doc/src/sgml : catalogs.sgml
> src/backend/bootstrap: bootstrap.c
> src/backend/catalog: pg_aggregate.c pg_proc.c
> src/backend/commands: functioncmds.c
> src/backend/nodes: copyfuncs.c equalfuncs.c
> src/backend/parser: gram.y
> src/backend/utils/adt: sets.c
> src/backend/utils/fmgr: fmgr.c
> src/include/catalog: catversion.h pg_attribute.h pg_class.h
> pg_proc.h
> src/include/nodes: nodes.h parsenodes.h
> src/pl/plperl : plperl.c
> src/pl/plpgsql/src: pl_comp.c
> src/pl/plpython: plpython.c
> src/pl/tcl : pltcl.c
>
> Log message:
> Apply the core parts of Dennis Bjorklund's patch to allow function
> parameters to be declared with names. pg_proc has a column to store
> names, and CREATE FUNCTION can insert data into it, but that's all as
> yet. I need to do more work on the pg_dump and plpgsql portions of the
> patch before committing those, but I thought I'd get the bulky changes
> in before the tree drifts under me.
> initdb forced due to pg_proc change.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
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