Re: DROP [TEMP] TABLE syntax, as reason why not?

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: DROP [TEMP] TABLE syntax, as reason why not?
Date: 2017-08-24 10:58:04
Message-ID: CA+bJJbxv0hqQsg+PO9BeTjuOK-nfXScaR_pPuFKf18WjnJ1Nqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Aug 24, 2017 at 12:48 PM, Vincenzo Romano
<vincenzo(dot)romano(at)notorand(dot)it> wrote:

> Isn't a CHOICE for better syntax enough?
> Aren't symmetry and consistency valuable arguments?
> Syntactic sugar is not evil on its own.
> It can help people writing code that can be better understood.

Valid arguments, but those extensions are NOT free to develop, test
and maintain. And every syntax extensions, specially one like this,
introduces the possibility of collisions with future standards ( de
facto or de iure, although Pg already deviates from ansi on the temp
stuff ).

Francisco Olarte.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-08-24 11:44:03 Re: 'value too long' and before insert/update trigger
Previous Message Francisco Olarte 2017-08-24 10:53:04 Re: DROP [TEMP] TABLE syntax, as reason why not?