Re: [PATCH] Provide support for trailing commas - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Provide support for trailing commas
Date
Msg-id f013ba17-82e6-48c9-b29b-cb0e274e2d37@eisentraut.org
Whole thread Raw
In response to Re: [PATCH] Provide support for trailing commas  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-hackers
On 23.03.26 23:54, Greg Sabino Mullane wrote:
> Alright, I walked through the entire list of every place the original 
> patch added a comma, and ruthlessly trimmed out the ones that were not 
> really needed, likely to cause issues, and/or frankly applied on too 
> trivial a piece of SQL to worry about. Here's my list that people can 
> poke at. Once we settle on which ones survive, I can make a new patch. 
> The focus is mostly on the largest potential uses: lists of select 
> items / column names.

I wrote:

 > I think there is consensus for allowing a trailing comma in the 
SELECT > list.  This would be the target_list production in gram.y.

I think that's the only one there is consensus about.

(But target_list is also used in RETURNING, so maybe the productions 
would need to be split up.)




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: add function argument name to substring and substr
Next
From: Antonin Houska
Date:
Subject: Re: Adding REPACK [concurrently]