public inbox for [email protected]  

help / color / mirror / Atom feed

From: David G. Johnston <[email protected]>
To: Tom Lane <[email protected]>
Cc: Andrey Borodin <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: GROUP BY ALL
Date: Sun, 18 Dec 2022 21:45:58 -0700
Message-ID: <CAKFQuwZQojxzMf3LYiNOO0dexn030tveM2K2_Qi8b0tud_CM2g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAhFRxjyTO5BHn9y1oOSEp0TtpTDTTTb7HJBNhTG+i3-hXC0XQ@mail.gmail.com>
	<[email protected]>

On Sunday, December 18, 2022, Tom Lane <[email protected]> wrote:

> Andrey Borodin <[email protected]> writes:
> > I saw a thread in a social network[0] about GROUP BY ALL. The idea seems
> useful.
>
> Isn't that just a nonstandard spelling of SELECT DISTINCT?
>
> What would happen if there are aggregate functions in the tlist?
> I'm not especially on board with "ALL" meaning "ALL (oh, but not
> aggregates)".
>
>
IIUC some systems treat any non-aggregated column as an implicit group by
column.  This proposal is an explicit way to enable that implicit behavior
in PostgreSQL.  It is, as you note, an odd meaning for the word ALL.

We tend to not accept non-standard usability syntax extensions even if
others systems implement them.  I don’t see this one ending up being an
exception…

David J.

view thread (42+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: GROUP BY ALL
  In-Reply-To: <CAKFQuwZQojxzMf3LYiNOO0dexn030tveM2K2_Qi8b0tud_CM2g@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox