From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
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 14:41:53 |
Message-ID: | CAHz80e5OR-aSijK5yU2bNrFXV2GKU9LUYHBMF52K+gFTu9i+qg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 14 Oct 2021 at 07:16, Gilles Darold <gilles(at)migops(dot)com> wrote:
> Hi,
>
> Here is a proposal to implement HIDDEN columns feature in PostgreSQL.
>
> 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.
>
The behaviour of SELECT * is well defined and consistent across many
databases, so I don't like changing the behaviour of it.
I would be in favour of a different symbol which expands to a more
selective column set. Perhaps by default it picks up short textish columns;
skip bytea or long text fields for example but can be adjusted with HIDDEN.
Perhaps "SELECT +"?
--
Rod Taylor
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2021-10-14 15:08:55 | Re: Next Steps with Hash Indexes |
Previous Message | Dave Page | 2021-10-14 13:38:13 | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |