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

From Stephen Frost
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 20091019162916.GL17756@tamriel.snowman.net
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Controlling changes in plpgsql variable resolution
List pgsql-hackers
* David E. Wheeler (david@kineticode.com) wrote:
> On Oct 19, 2009, at 8:36 AM, Robert Haas wrote:
>
>> I think warnings are too easy to miss, but I agree your other
>> suggestion.  I know you can write function_name.variable_name, but
>> that's often massively long-winded.  We either need a short, fixed
>> prefix, or some kind of sigil.  I previously suggested ? to parallel
>> ECPG, but Tom didn't like it.  I still do.  :-)
>
> I suppose that $ would interfere with dollar quoting. What about @ or @@
> (sorry, I did mess with MSSQL back in the 90s).

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?).
Stephen

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Controlling changes in plpgsql variable resolution
Next
From: Andrew Dunstan
Date:
Subject: Re: Rejecting weak passwords