Re: Specific names for plpgsql variable-resolution control options?

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Specific names for plpgsql variable-resolution control options?
Дата
Msg-id 20091109004748.GA9601@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: Specific names for plpgsql variable-resolution control options?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Specific names for plpgsql variable-resolution control options?
Список pgsql-hackers
Tom Lane wrote:
> "David E. Wheeler" <david@kineticode.com> writes:
> > That works.
> 
> >    plpgsql_variable_conflict = fatal | variable-first | column-first
> 
> If we do that, presumably the per-function syntax would be
> 
>     #variable_conflict variable_first
> 
> and so on, which is clear enough but might be thought a bit verbose
> for something people might be pasting into hundreds of functions.

If there's some way to "paste" it automatically (like, say, an
appropriate UPDATE incantation on pg_proc) then that doesn't seem like
an important problem.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: [PATCH] tsearch parser inefficiency if text includes urls or emails - new version
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Specific names for plpgsql variable-resolution control options?