Re: Controlling changes in plpgsql variable resolution - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 648039E0-80A3-4F4F-9806-EC746FB3F6B5@kineticode.com
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Controlling changes in plpgsql variable resolution
List pgsql-hackers
On Oct 19, 2009, at 9:49 AM, Tom Lane wrote:

>> I'd sure love $, as it's like shell, Perl, and other stuff.
>
> This discussion has gotten utterly off track.  The problem I am trying
> to solve is a non-Oracle-compatible behavior in plpgsql.  I have got
> substantially less than zero interest in proposals that "solve" the
> problem by introducing notations that don't even pretend to be
> compatible.

Party pooper.

I'd be in favor of a GUC that I could turn on to throw an error when  
there's an ambiguity. As for which way it should go, I have no dog in  
that pony hunt. Or something.

Best,

David


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Controlling changes in plpgsql variable resolution
Next
From: Dean Rasheed
Date:
Subject: Re: Scaling up deferred unique checks and the after trigger queue