Re: pl/pgsql breakage in 8.1b4?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Yarra <philip(at)utiba(dot)com>
Cc: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pl/pgsql breakage in 8.1b4?
Date: 2005-10-28 04:10:00
Message-ID: 26490.1130472600@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Yarra <philip(at)utiba(dot)com> writes:
> Without really wishing to volunteer myself: should plpgsql allow using
> parameters with the same name as the columns being referred to within the
> function, provided they're qualified as function_name.parameter?

No, because that just changes where the ambiguity is. The function name
could easily conflict with a table name. It's a mighty weird-looking
convention anyway --- on what grounds would you argue that the function
is a structure having parameter names as fields?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2005-10-28 04:14:56 Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", File: "nbtsearch.c", Line: 89)
Previous Message Philip Yarra 2005-10-28 03:54:27 Re: pl/pgsql breakage in 8.1b4?