Re: Why forbid "INSERT INTO t () VALUES ();" - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why forbid "INSERT INTO t () VALUES ();"
Date
Msg-id CA+TgmoaGrSL_BFttkUO-WLga0gdG2QNBDsDgTRXE1U0=Kr5Q_Q@mail.gmail.com
Whole thread Raw
In response to Re: Why forbid "INSERT INTO t () VALUES ();"  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: Why forbid "INSERT INTO t () VALUES ();"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jun 25, 2020 at 12:56 AM Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> It also means that if for some reason someone wants to insert several such
> all-default rows, they have to repeat the insert, as "VALUES (), ();"
> would not work, so it is also losing a corner-corner case capability
> without obvious reason.

That, and a desire to make things work in PostgreSQL that work in
MySQL, seems like a good-enough reason to me, but YMMV.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: improving basebackup.c's file-reading code
Next
From: Robert Haas
Date:
Subject: Re: improving basebackup.c's file-reading code