Re: group by true now errors with non-integer constant in GROUP BY

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Dennis Brouwer <dennis(dot)brouwer(at)kizitos(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, David Micallef <david(dot)j(dot)micallef(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: group by true now errors with non-integer constant in GROUP BY
Date: 2023-10-20 06:20:27
Message-ID: cf93e3c0-dcfe-4d8e-bd10-0c2d0caad3f8@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 10/20/23 07:44, Vik Fearing wrote:
> I may have oversimplified this example, but as long as the value is
> present in the SELECT, logic would dictate that we can group by it.

Oops, I have this backwards: the projection comes after the grouping.
--
Vik Fearing

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Laurenz Albe 2023-10-20 06:32:57 Re: group by true now errors with non-integer constant in GROUP BY
Previous Message Vik Fearing 2023-10-20 05:44:23 Re: group by true now errors with non-integer constant in GROUP BY