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

From Vik Fearing
Subject Re: Why forbid "INSERT INTO t () VALUES ();"
Date
Msg-id d3f60110-f283-ebb9-9888-b857c7701048@postgresfriends.org
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 ();"  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On 6/25/20 6:56 AM, Fabien COELHO wrote:
> 
> Hello Tom,
> 
>>>>>   INSERT INTO t() VALUES ();
>>
>>> I'm still unclear why it would be forbidden though, it seems logical to
>>> try that, whereas the working one is quite away from the usual syntax.
>>
>> It's forbidden because the SQL standard forbids it.
> 
> Ok, that is definitely a reason. I'm not sure it is a good reason, though.


It's a very good reason.  It might not be good *enough*, but it is a
good reason.


> Why would the standard forbid it? From the language design point of
> view[...]


Don't go there.  There is nothing but pain there.

-- 
Vik Fearing



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Review for GetWALAvailability()
Next
From: Amit Kapila
Date:
Subject: Re: Backpatch b61d161c14 (Introduce vacuum errcontext ...)