MIME-Version: 1.0
References: <CAHM0NXjz0kDwtzoe-fnHAqPB1qA8_VJN0XAmCgUZ+iPnvP5LbA@mail.gmail.com>
In-Reply-To: <CAHM0NXjz0kDwtzoe-fnHAqPB1qA8_VJN0XAmCgUZ+iPnvP5LbA@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Mon, 22 Jul 2024 14:33:57 -0700
Message-ID: <CAKFQuwY0vhNG8T+pC3BQJurFi3NN_L1KbEPGagRN3V5nKZcpDQ@mail.gmail.com>
Subject: Re: [PATCH] GROUP BY ALL
To: David Christensen <david@pgguru.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000bf03cc061ddccfb5"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwY0vhNG8T%2BpC3BQJurFi3NN_L1KbEPGagRN3V5nKZcpDQ%40mail.gmail.com>
Precedence: bulk

--000000000000bf03cc061ddccfb5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 22, 2024 at 1:55=E2=80=AFPM David Christensen <david@pgguru.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.

--000000000000bf03cc061ddccfb5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Mon, Jul 22, 2024 at 1:55=E2=80=AFPM David Christensen =
&lt;<a href=3D"mailto:david@pgguru.net">david@pgguru.net</a>&gt; wrote:</sp=
an><br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">I see that there&#39;d been some chatter but not a lot=
 of discussion about<br>
a GROUP BY ALL feature/functionality.=C2=A0 There certainly is utility in<b=
r>
such a construct IMHO.<br><br>
Still need some docs; just throwing this out there and getting some feedbac=
k.<br><br></blockquote><div><br></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif">I strongly dislike adding this fea=
ture.=C2=A0 I&#39;d only consider supporting it if it was part of the SQL s=
tandard.</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:arial,helvetica,sans-serif">Code is written once and read many=C2=A0times=
.=C2=A0 This feature caters to the=C2=A0writer, not the=C2=A0reader.=C2=A0 =
And furthermore usage of this is prone to be to the writer&#39;s detriment =
as well.</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:arial,helvetica,sans-serif">David J.</div><div class=3D"gmail_default" st=
yle=3D"font-family:arial,helvetica,sans-serif"><br></div></div></div>

--000000000000bf03cc061ddccfb5--