Re: proposal sql: labeled function params - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal sql: labeled function params
Date
Msg-id 162867790808200626w40350731gc0602099ce3d8e18@mail.gmail.com
Whole thread Raw
In response to Re: proposal sql: labeled function params  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal sql: labeled function params  ("Asko Oja" <ascoja@gmail.com>)
Re: proposal sql: labeled function params  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
2008/8/20 Tom Lane <tgl@sss.pgh.pa.us>:
> "Pavel Stehule" <pavel.stehule@gmail.com> writes:
>> I understand now why Oracle use => symbol for named params. This isn't
>> used so operator - so implementation is trivial.
>
> You really didn't understand the objection at all, did you?
>
> The point is not about whether there is any built-in operator named =>.
> The point is that people might have created user-defined operators named
> that.

I understand well, so only I don't see better solution. Yes, everyone
who used => should have problems, but it is similar with .. new
keywords, etc. Probably easy best syntax doesn't exist :(. I  haven't
idea who use => now and how often, and if this feature is possible in
pg, but there are not technical barriers.

regards
Pavel Stehule


>
>                        regards, tom lane
>


pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: Patch: plan invalidation vs stored procedures
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: A smaller default postgresql.conf