Re: [PATCH] Proposal for HIDDEN/INVISIBLE column - Mailing list pgsql-hackers

From Gilles Darold
Subject Re: [PATCH] Proposal for HIDDEN/INVISIBLE column
Date
Msg-id 1b1d4fcf-1b73-243e-9930-dd1c810a2405@migops.com
Whole thread Raw
In response to Re: [PATCH] Proposal for HIDDEN/INVISIBLE column  (Isaac Morland <isaac.morland@gmail.com>)
Responses Re: [PATCH] Proposal for HIDDEN/INVISIBLE column  (Vik Fearing <vik@postgresfriends.org>)
List pgsql-hackers
Le 17/10/2021 à 23:48, Isaac Morland a écrit :
On Sun, 17 Oct 2021 at 17:42, Gilles Darold <gilles@migops.com> wrote:

Perhaps I misunderstand what you are saying, but a no-columns table definitely can return rows:

psql (12.2)
Type "help" for help.

postgres=# create table nada ();
CREATE TABLE
postgres=# insert into nada default values;
INSERT 0 1
postgres=# insert into nada default values;
INSERT 0 1
postgres=# table nada;
--
(2 rows)

postgres=#

Note that psql doesn't display a separate line for each row in this case, but the actual result coming back from the server does contain the appropriate number of rows. 


I was not aware of that. In this case perhaps that we can remove the restriction on having at least on expandable column and we will have the same behavior but I can't think of an interest to allow that.


-- 
Gilles Darold

pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Added schema level support for publication.
Next
From: Michael Paquier
Date:
Subject: Re: try_relation_open and relation_open behave different.