| From: | Roberto Mello <roberto(dot)mello(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why do OLD and NEW have special internal names? |
| Date: | 2009-11-06 12:06:12 |
| Message-ID: | 42d652c70911060406q226a7498vd42c2cbe2b2bed01@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 5, 2009 at 5:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> BTW, this brings up another point, which is that up to now it's often
> been possible to use plpgsql variable names that conflict with
> core-parser reserved words, so long as you didn't need to use the
> reserved word with its special meaning. That will stop working when
> this patch goes in. Doesn't bother me any, but if anyone thinks it's
> a serious problem, speak now.
I imagine there will be a small percentage of PL/pgSQL users that will
be afected, so these changes must be well written up in the PL/pgSQL
documentation.
Roberto
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-11-06 12:22:55 | Re: Why do OLD and NEW have special internal names? |
| Previous Message | Tom Lane | 2009-11-06 06:09:57 | Re: Freebsd & autoconf-2.63 |