Re: plpgsql + named parameters - Mailing list pgsql-hackers

From Steve Prentice
Subject Re: plpgsql + named parameters
Date
Msg-id 23DAA99A-B116-4EEE-A64A-AE95047B70F9@cisco.com
Whole thread Raw
In response to Re: plpgsql + named parameters  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: plpgsql + named parameters  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Documentation: GiST extension implementation
Next
From: Pavel Stehule
Date:
Subject: Re: plpgsql + named parameters