Re: Controlling changes in plpgsql variable resolution

2009/10/19 Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>:
> "David E. Wheeler" <david(at)kineticode(dot)com> wrote:
>
>> I'd be in favor of a GUC that I could turn on to throw an error
>> when there's an ambiguity.
>
> I would consider hiding one definition with another very bad form, so
> I would prefer to have plpgsql throw an error when that happens.  I
> don't particularly care whether that is the only supported behavior or
> whether there's a GUC to control it, or what its default is, if
> present.
>

ambiguous identifiers is probably the top reason of some plpgsql's
mysterious errors. More times I found wrong code - sometime really
important (some security checks). I never found good code with
ambiguous identifiers - so for me, exception is good. But - there will
be lot of working applications that contains this hidden bug - and
works "well". So it could be a problem. GUC should be a solution.

Pavel

> -Kevin
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>