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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-25 14:51:11
Message-ID: CA+TgmoaGrSL_BFttkUO-WLga0gdG2QNBDsDgTRXE1U0=Kr5Q_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 25, 2020 at 12:56 AM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-06-25 14:54:37 Re: improving basebackup.c's file-reading code
Previous Message Daniel Gustafsson 2020-06-25 14:29:48 Re: improving basebackup.c's file-reading code