Re: WIP: Allow SQL-language functions to reference parameters by parameter name

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: David Fetter <david(at)fetter(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Matthew Draper <matthew(at)trebex(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: Allow SQL-language functions to reference parameters by parameter name
Date: 2011-03-27 14:45:19
Message-ID: 4D8F4D7F.3020301@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/27/2011 09:42 AM, David Fetter wrote:
> On Fri, Mar 25, 2011 at 09:12:33PM -0400, Robert Haas wrote:
>> As I've said before, I believe that the root cause of this problem is
>> that using the same syntax for variables and column names is a bad
>> idea in the first place. If we used $foo or ?foo or ${foo} or $.foo
>> or&&foo!!$#? to mean "the parameter called foo", then this would all
>> be a non-issue.
> How about psql's :foo syntax?
>
>

Surely the time has long gone when we could have made such a choice. And
the choice was not made in a vacuum.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message 3dmashup 2011-03-27 14:57:16 Re: Needs Suggestion
Previous Message David Fetter 2011-03-27 13:42:33 Re: WIP: Allow SQL-language functions to reference parameters by parameter name