| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Controlling changes in plpgsql variable resolution |
| Date: | 2009-10-19 16:52:59 |
| Message-ID: | 648039E0-80A3-4F4F-9806-EC746FB3F6B5@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-19 17:02:37 | Re: Scaling up deferred unique checks and the after trigger queue |
| Previous Message | Tom Lane | 2009-10-19 16:49:19 | Re: Controlling changes in plpgsql variable resolution |