Re: Controlling changes in plpgsql variable resolution

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: 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:25:02
Message-ID: 264673D1-9613-43BF-BB4B-F95B2DEDA283@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 19, 2009, at 7:54 AM, Stephen Frost wrote:

> 4. Resolve ambiguous names as query column, but throw warning
>
> #4 would be my vote, followed by #3. To be perfectly honest, I'd be a
> whole lot happier with a pl/pgsql that let me prefix variable names
> with
> a '$' or similar to get away from this whole nonsense. I've been very
> tempted to tell everyone I work with to start prefixing their
> variables
> names with '_' except that it ends up looking just plain ugly.

+1, just what I was thinking.

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2009-10-19 16:27:21 Re: Controlling changes in plpgsql variable resolution
Previous Message Alvaro Herrera 2009-10-19 16:23:00 Re: Rejecting weak passwords