From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
Cc: | Gilles Darold <gilles(at)migops(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Proposal for HIDDEN/INVISIBLE column |
Date: | 2021-10-15 17:34:03 |
Message-ID: | CAOBaU_ayXL=FCx5_wrnZbC0UnajdUX=hd286Y3GowLDEtO0KtA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 15, 2021 at 9:40 PM Dave Cramer <davecramer(at)postgres(dot)rocks> wrote:
>
> On Fri, 15 Oct 2021 at 09:29, Gilles Darold <gilles(at)migops(dot)com> wrote:
>>
>> Yes, I don't wanted to offend you or to troll. This was just to point
>> that the position of "SELECT * is bad practice" is not a good argument
>> in my point of view, just because it is allowed for every one. I mean
>> that in an extension or a client which allow user query input we must
>> handle the case.
>
> This would break an awful lot of apps.
Which is also why allowing to hide some custom columns from a "SELECT
*" powerful. It's no doubt a niche usage, but as Gilles mentioned
extensions can make use of that to build interesting things. If DBA
can also make use of it to ease manual queries if the client apps are
correctly written, that's icing on the cake.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2021-10-15 17:52:06 | Re: should we allow users with a predefined role to access pg_backend_memory_contexts view and pg_log_backend_memory_contexts function? |
Previous Message | Jeff Davis | 2021-10-15 17:26:16 | Re: should we allow users with a predefined role to access pg_backend_memory_contexts view and pg_log_backend_memory_contexts function? |