Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.
Date: 2006-06-15 19:21:18
Message-ID: 200606151921.k5FJLIP17591@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> The odds of that syntax getting accepted may not be exactly zero, but
> >> they are certainly vanishingly small. I thought we'd agreed that a
> >> usable syntax would be like
> >> get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
>
> > TODO updated, but I thought "=>" was the Oracle syntax.
>
> So? We don't support Oracle's brain-dead outer join syntax either.

We had reasonable problems with Oracle's outer-join syntax, while I
don't see the same fundamental issue with => vs AS, and PL/pgSQL is
patterned on Oracle's PL/SQL.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-06-15 19:36:43 Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.
Previous Message Tom Lane 2006-06-15 19:19:45 Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.