Re: Why forbid "INSERT INTO t () VALUES ();"

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Thomas Kellerer <shammat(at)gmx(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Why forbid "INSERT INTO t () VALUES ();"
Date: 2020-06-26 07:09:07
Message-ID: 54bcfb48-8b05-938a-20f8-537f3785dee3@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-06-25 18:07, Tom Lane wrote:
> So I'm still not convinced we should do this. "MySQL is incapable
> of conforming to the standard" is a really lousy reason for us to do
> something.

Conformance to the standard means that the syntax described in the
standard behaves as specified in the standard. It doesn't mean you
can't have additional syntax that is not in the standard.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-06-26 07:14:38 Re: [patch] demote
Previous Message Michael Banck 2020-06-26 06:45:53 Re: [Patch] ALTER SYSTEM READ ONLY