Re: [PATCH] 8.5 plpgsql change for named notation: treat word following AS keyword as label v2

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Steve Prentice <prentice(at)cisco(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] 8.5 plpgsql change for named notation: treat word following AS keyword as label v2
Date: 2009-05-22 15:28:47
Message-ID: 20090522152847.GA4466@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:
> On 5/21/09 6:44 PM, Alvaro Herrera wrote:
>> Josh Berkus wrote:
>>>> The patch adds the "AS" keyword to the plpgsql grammar and doesn't
>>>> assign an expression parameter to the sql construct if the scalar
>>>> follows the AS keyword.
>>> Would it be possible to also support "=" as well as "as"? I believe
>>> that SQL Server uses "=" exclusively, and supporting that syntax would
>>> help people port TSQL-based applications.
>>
>> Would this be best served by implementing PL/TSQL?
>
> Passing variables takes place *outside* of the PL.

Hmm, sure, but I was actually thinking on a higher level ... I mean I've always
thought that there's so much effort directed at porting procedures from TSQL to
plpgsql, but it would be better to just write a dedicated PL. (Of course,
the set of people who can actually write such a PL is a lot smaller than those
who can write plpgsql).

I mean if all you had to do was change = to "as" to make your TSQL procedures
supported, you'd be a lot happier than if that was the only work you could
_save_.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-05-22 15:43:34 Re: patch for ja.po
Previous Message Konstantin Izmailov 2009-05-22 15:27:01 information_schema.columns changes needed for OLEDB