Re: PL/pgSQL 2 - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: PL/pgSQL 2
Date
Msg-id CAASwCXc=yBMyD+FtWPV9b8JE8DUabYrEMnci4+eqKptexY5k2w@mail.gmail.com
Whole thread Raw
In response to Re: PL/pgSQL 2  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: PL/pgSQL 2  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Re: PL/pgSQL 2  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers
On Tue, Sep 2, 2014 at 3:41 PM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> On 09/02/2014 04:32 PM, Joel Jacobson wrote:
>> I think it's much better to make it the default behaviour in plpgsql2
>> than to add a new syntax to plpgsql,
>> because then we don't have to argue what to call the keyword or where to
>> put it.
>
>
> Then you'll have to argue what the *other* syntax should look like. And not
> everyone agrees on the default either, see Kevin's email. Designing a new
> language is going to be an uphill battle, even more so than enhancing
> current plpgsql.

Any ideas on what the *other* syntax could look like?



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch for psql History Display on MacOSX
Next
From: Heikki Linnakangas
Date:
Subject: Re: PL/pgSQL 2