| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Gilles Darold <gilles(at)migops(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |
| Date: | 2021-10-18 15:24:38 |
| Message-ID: | 2f9f7a18-f3df-e058-c5ed-d73033e11610@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/18/21 8:44 AM, Gilles Darold wrote:
> Le 17/10/2021 à 23:48, Isaac Morland a écrit :
>> On Sun, 17 Oct 2021 at 17:42, Gilles Darold <gilles(at)migops(dot)com
>> <mailto:gilles(at)migops(dot)com>> wrote:
>>
>> 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.
Allowing no-column tables removed the need to handle a bunch of corner
cases. Useful for users or not, the precedent is set.
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-10-18 15:45:20 | Re: when the startup process doesn't (logging startup delays) |
| Previous Message | Alvaro Herrera | 2021-10-18 14:45:28 | Re: modify error report in mdwrite/mdextend |