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

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Specific names for plpgsql variable-resolution control options?
Date: 2009-11-07 03:09:46
Message-ID: 6F599E44-6EE0-4361-9CA0-0D294571B08D@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-11-07 07:11:22 Re: Why do OLD and NEW have special internal names?
Previous Message Tom Lane 2009-11-07 02:57:13 Re: Specific names for plpgsql variable-resolution control options?