From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, Gilles Darold <gilles(at)migops(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |
Date: | 2021-10-14 12:28:32 |
Message-ID: | CAFj8pRC=j_d2Htnx048ar5Qr4As7VW6wUiBQ17FxFv0L3oJcaw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
čt 14. 10. 2021 v 14:13 odesílatel Vik Fearing <vik(at)postgresfriends(dot)org>
napsal:
> On 10/14/21 1:47 PM, Aleksander Alekseev wrote:
> > Hi Gilles,
> >
> >> Any though and interest in this feature?
> >
> > Personally, I wouldn't call this feature particularly useful. `SELECT
> > *` is intended for people who are working with DBMS directly e.g. via
> > psql and want to see ALL columns.
>
> I disagree strongly with this. It is really annoying when working
> interactively with psql on a table that has a PostGIS geometry column,
> or any other large blobby type column.
>
> I have not looked at the patch, but +1 for the feature.
>
Cannot be better to redefine some strategies for output for some types.
I can agree so sometimes in some environments proposed features can be
nice, but it can be a strong footgun too.
Maybe some strange data can be filtered in psql and it can be better
solution. I agree, so usually print long geometry in psql is useless.
Regards
Pavel
--
> Vik Fearing
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Isaac Morland | 2021-10-14 12:28:48 | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |
Previous Message | Aleksander Alekseev | 2021-10-14 12:21:42 | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |