Re: Controlling changes in plpgsql variable resolution

Поиск
Список
Период
Сортировка
От David E. Wheeler
Тема Re: Controlling changes in plpgsql variable resolution
Дата
Msg-id 648039E0-80A3-4F4F-9806-EC746FB3F6B5@kineticode.com
обсуждение исходный текст
Ответ на Re: Controlling changes in plpgsql variable resolution  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Controlling changes in plpgsql variable resolution  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Controlling changes in plpgsql variable resolution
Следующее
От: Dean Rasheed
Дата:
Сообщение: Re: Scaling up deferred unique checks and the after trigger queue