| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Specific names for plpgsql variable-resolution control options? |
| Date: | 2009-11-09 00:47:49 |
| Message-ID: | 20091109004748.GA9601@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-09 01:16:47 | Re: Specific names for plpgsql variable-resolution control options? |
| Previous Message | Andres Freund | 2009-11-08 23:03:10 | Re: [PATCH] tsearch parser inefficiency if text includes urls or emails - new version |