Re: group by true now errors with non-integer constant in GROUP BY - Mailing list pgsql-bugs

From David Rowley
Subject Re: group by true now errors with non-integer constant in GROUP BY
Date
Msg-id CAApHDvrJBCJkahy+LoPqBZ2ETj9-2FuuWj-ct-EKjFJnqZ19dQ@mail.gmail.com
Whole thread Raw
In response to Re: group by true now errors with non-integer constant in GROUP BY  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-bugs
On Thu, 21 Sept 2023 at 16:58, Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Sun, Sep 17, 2023 at 5:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > FTR, I still think this is a bad idea.  It will add more confusion
> > than it removes, and I don't buy that it will confer any advantages,
> > because nobody asked for it previously.
>
> I agree. Maintaining bug compatibility doesn't seem worth it in this instance.

Thanks for chipping in.

Just for the record, I'm more keen on removing the special case that
disallows this.  For me it's more about POLA.  I expect that anywhere
I can write an expression in SQL, that I can put a Const in its place
and not receive an error to say constants are disallowed.

I mentioned this to Andres in a meeting yesterday and it seems to be
against allowing Consts, so I seem to be losing this one.

David



pgsql-bugs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: BUG #18118: bug report for COMMIT AND CHAIN feature
Next
From: "刘相(佑熙)"
Date:
Subject: 回复:Re: BUG #18118: bug report for COMMIT AND CHAIN feature