| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Gilles Darold <gilles(at)migops(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |
| Date: | 2021-10-14 12:28:48 |
| Message-ID: | CAMsGm5fXSz5avkzuTrZM3k9nNyW1ahOcN_6XQipcw_-WPwfv6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 14 Oct 2021 at 07:17, Gilles Darold <gilles(at)migops(dot)com> wrote:
> The user defined columns are always visible in the PostgreSQL. If user
> wants to hide some column(s) from a SELECT * returned values then the
> hidden columns feature is useful. Hidden column can always be used and
> returned by explicitly referring it in the query.
>
It seems to me we've gone in the reverse direction recently. It used to be
that the oid columns of the system tables were hidden (hardcoded, as far as
I know), but as of Postgres 12 I believe there are no more hidden columns:
SELECT * from a table always gives all the columns.
I think a "select all columns except …" would be more useful; or another
approach would be to use a display tool that defaults to displaying only a
portion of large fields.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amul Sul | 2021-10-14 12:44:20 | Re: prevent immature WAL streaming |
| Previous Message | Pavel Stehule | 2021-10-14 12:28:32 | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |