From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |
Date: | 2021-10-14 20:01:59 |
Message-ID: | 71e75ae4-a6a2-7fdc-89e3-2f7ebebf04ae@archidevsys.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 15/10/21 07:01, Josef Šimánek wrote:
> čt 14. 10. 2021 v 13:17 odesílatel Gilles Darold <gilles(at)migops(dot)com> napsal:
>> 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.
>>
>> I agree that views are done for that or that using a SELECT * is a bad
>> practice
>> but sometime we could need to "technically" prevent some columns to be part
>> of a star expansion and nbot be forced to use view+rules.
> Just to remind here, there was recently a proposal to handle this
> problem another way - provide a list of columns to skip for "star
> selection" aka "SELECT * EXCEPT col1...".
>
> https://postgrespro.com/list/id/d51371a2-f221-1cf3-4a7d-b2242d4dafdb(at)gmail(dot)com
[...]
I feel using EXCEPT would be a lot clearer, no one is likely to be
mislead into thinking that its is a security feature unlike 'HIDDEN'.
Also you know that SELECT * will select all columns.
If this kind of feature were to be added, then I'd give a +1 to use the
EXCEPT syntax.
Cheers,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2021-10-14 20:18:29 | Re: Gather performance analysis |
Previous Message | Josef Šimánek | 2021-10-14 19:36:52 | Re: [RFC] building postgres with meson |