Re: Specific names for plpgsql variable-resolution control options? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Specific names for plpgsql variable-resolution control options?
Date
Msg-id 20091109004748.GA9601@alvh.no-ip.org
Whole thread Raw
In response to Re: Specific names for plpgsql variable-resolution control options?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Specific names for plpgsql variable-resolution control options?
List 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 by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] tsearch parser inefficiency if text includes urls or emails - new version
Next
From: Tom Lane
Date:
Subject: Re: Specific names for plpgsql variable-resolution control options?