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

From David E. Wheeler
Subject Re: Specific names for plpgsql variable-resolution control options?
Date
Msg-id 6F599E44-6EE0-4361-9CA0-0D294571B08D@kineticode.com
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
On Nov 6, 2009, at 6:57 PM, Tom Lane wrote:

> 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.

I suspect that most folks will set the GUC and few will actually use  
it in functions. Just my guess though.

David


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Specific names for plpgsql variable-resolution control options?
Next
From: David Fetter
Date:
Subject: Re: Why do OLD and NEW have special internal names?