Re: plpgsql + named parameters

From: Steve Prentice <prentice(at)cisco(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: plpgsql + named parameters
Date: 2009-05-20 16:57:44
Message-ID: 23DAA99A-B116-4EEE-A64A-AE95047B70F9@cisco.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> t := fun1(1 as a); -- syntax error: "SELECT fun1(1 as
>> $1 )"
>> t := fun1(a as a); -- syntax error: "SELECT fun1( $1
>> as $1 )"

On May 19, 2009, at 6:42 PM, Merlin Moncure wrote:
> you have a name conflict here...is it deliberate? I've learned the
> hard way to always, always prefix arguments and locals to plpgsql
> functions with '_'. Or are you trying to do something fancier?

The conflict is deliberate to illustrate the limitations the named
parameter feature (on the list for the first 8.5 CommitFest) is going
to have if parameter substitution is not addressed at the same time.

-Steve

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2009-05-20 17:24:35 Re: plpgsql + named parameters
Previous Message Dimitri Fontaine 2009-05-20 16:10:53 Re: Documentation: GiST extension implementation