Re: New.* and old.* as function arguments within rules - Mailing list pgsql-general

From Karl O. Pinc
Subject Re: New.* and old.* as function arguments within rules
Date
Msg-id 1133674121l.28211l.6l@mofo
Whole thread Raw
In response to Re: New.* and old.* as function arguments within rules  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 12/03/2005 10:29:43 PM, Tom Lane wrote:
> "Karl O. Pinc" <kop@meme.com> writes:
> > 2nd, nowhere have I found a NEW.* syntax (as written).

> In general, "foo.*" where foo is a visible table alias is meaningful
> anywhere that a rowtype value would be accepted.  There is a special
> case at the top level of a SELECT result list, where it will be broken
> apart into a list of foo's component fields because the SQL spec says
> so.

Thanks very much.  I had just started writing 'foo' because I didn't
know about 'foo.*' and it's been working so far (8.0.3) but
would _hate_ to have it break on upgrade.

This is the first time I've found the Postgres documentation to be
really lacking.  I suppose there has to be a first.
(Very sorry, _wway_ to busy to write a doc patch.)

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein


pgsql-general by date:

Previous
From: Jan Wieck
Date:
Subject: Re: 8.03 versus 8.04
Next
From: "Karl O. Pinc"
Date:
Subject: Use of %ROWTYPE in plpgsql function declarations