| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | David Christensen <david(at)pgguru(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] GROUP BY ALL |
| Date: | 2024-07-22 21:33:57 |
| Message-ID: | CAKFQuwY0vhNG8T+pC3BQJurFi3NN_L1KbEPGagRN3V5nKZcpDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 22, 2024 at 1:55 PM David Christensen <david(at)pgguru(dot)net> wrote:
> I see that there'd been some chatter but not a lot of discussion about
> a GROUP BY ALL feature/functionality. There certainly is utility in
> such a construct IMHO.
>
> Still need some docs; just throwing this out there and getting some
> feedback.
>
>
I strongly dislike adding this feature. I'd only consider supporting it if
it was part of the SQL standard.
Code is written once and read many times. This feature caters to
the writer, not the reader. And furthermore usage of this is prone to be
to the writer's detriment as well.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-07-22 21:36:33 | Re: Remove dependence on integer wrapping |
| Previous Message | Andreas Karlsson | 2024-07-22 21:25:07 | Re: Special-case executor expression steps for common combinations |