Re: [REVIEW] Patch for cursor calling with named parameters - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: [REVIEW] Patch for cursor calling with named parameters
Date
Msg-id DB8FC58A-4C21-4C43-BC44-8EB76F40394E@kineticode.com
Whole thread Raw
In response to Re: [REVIEW] Patch for cursor calling with named parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Oct 6, 2011, at 10:46 AM, Tom Lane wrote:

>> Okay. I kind of like := so there's no rush AFAIC. :-)
>
> Hmm ... actually, that raises another issue that I'm not sure whether
> there's consensus for or not.  Are we intending to keep name := value
> syntax forever, as an alternative to the standard name => value syntax?
> I can't immediately see a reason not to, other than the "it's not
> standard" argument.

The only reason it would be required, I think, is if the SQL standard developed some other use for that operator.

> Because if we *are* going to keep it forever, there's no very good
> reason why we shouldn't accept this plpgsql cursor patch now.  We'd
> just have to remember to extend plpgsql to take => at the same time
> we do that for core function calls.

Makes sense.

Best,

David



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [REVIEW] Patch for cursor calling with named parameters
Next
From: Robert Haas
Date:
Subject: Re: [REVIEW] Patch for cursor calling with named parameters