On Mon, May 23, 2016 at 1:44 PM, David Fetter <da...@fetter.org> wrote:
> On Mon, May 23, 2016 at 01:36:57PM -0400, Tom Lane wrote: > > David Fetter <da...@fetter.org> writes: > > > On Mon, May 23, 2016 at 01:10:29PM -0400, Tom Lane wrote: > > >> This seems a bridge too far to me. It's just way too common to do > > >> "select generate_series(1,n)". We could tell people they have to > > >> rewrite to "select * from generate_series(1,n)", but it would be far > > >> more polite to do that for them. > > > > > How about making "TABLE generate_series(1,n)" work? It's even > > > shorter in exchange for some cognitive load. > > > > No thanks --- the word after TABLE ought to be a table name, not some > > arbitrary expression. That's way too much mess to save one keystroke. > > It's not just about saving a keystroke. This change would go with > removing the ability to do SRFs in the target list of a SELECT > query. > If you want to make an argument for doing this regardless of the target list SRF change by all means - but it does absolutely nothing to mitigate the breakage that would result if we choose this path. David J.