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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Specific names for plpgsql variable-resolution control options?
Date: 2009-11-07 02:57:13
Message-ID: 13811.1257562633@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David E. Wheeler" <david(at)kineticode(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2009-11-07 03:09:46 Re: Specific names for plpgsql variable-resolution control options?
Previous Message Tom Lane 2009-11-07 02:54:40 Re: operator exclusion constraints