Re: named parameters in SQL functions

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: named parameters in SQL functions
Date: 2009-11-16 03:00:27
Message-ID: 603c8f070911151900t9e9bb37ka8d80f3ed352e6e2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 15, 2009 at 9:52 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Robert Haas wrote:
>>>
>>> (But having said that, an alternate qualification name is something
>>> that could be implemented if there were any agreement on what to use.)
>>>
>>
>> Well that is the tricky part, for sure.  I would personally prefer
>> something like ${name} rather than a prefix, but I think you're likely
>> to veto that outright.  So, anything reasonably short would be an
>> improvement over the status quo.  self?  this?  my?
>
> I think it would have to be a reserved word. The obvious existing keyword to
> use is "function" but unless I'm mistaken we'd need to move it from
> unreserved keyword to reserved, and I'm not sure this would justify that.

I don't see why it would need to be a reserved word. We're not
changing how it gets parsed, just what it means. At any rate
"FUNCTION." is a 9-character prefix, which is rather longer than I
would prefer. PL/pgsql is a tiresomely long-winded language in
general, IMHO, although some of Tom's changes for 8.5 will help with
that.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-16 03:04:11 Re: named parameters in SQL functions
Previous Message Andrew Dunstan 2009-11-16 02:52:54 Re: named parameters in SQL functions