| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Controlling changes in plpgsql variable resolution |
| Date: | 2009-10-19 16:42:02 |
| Message-ID: | 303C35F1-A524-499E-91D8-B218861E4801@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 19, 2009, at 9:29 AM, Stephen Frost wrote:
> Uh, what dollar quoting? $_$ is what I typically use, so I wouldn't
> expect a $ prefix to cause a problem. I think it'd be more of an
> issue
> because pl/pgsql still uses $1 and whatnot internally (doesn't it?).
Yes, but that's no more an issue than it is in Perl, where the same $n
variables are globals. The issue with dollar quoting is that you can
put anything between the dollar signs. So if you have two $variables,
they can get in the way. Potentially. But perhaps the lexer and/or
Parser won't be confused by that, Tom?
I'd sure love $, as it's like shell, Perl, and other stuff.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2009-10-19 16:48:46 | Re: Scaling up deferred unique checks and the after trigger queue |
| Previous Message | Pavel Stehule | 2009-10-19 16:38:05 | Re: Application name patch - v2 |