Re: Controlling changes in plpgsql variable resolution - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 303C35F1-A524-499E-91D8-B218861E4801@kineticode.com
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Controlling changes in plpgsql variable resolution
List 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


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Application name patch - v2
Next
From: Tom Lane
Date:
Subject: Re: Controlling changes in plpgsql variable resolution