From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Changed SRF in targetlist handling |
Date: | 2016-05-23 17:44:20 |
Message-ID: | 20160523174420.GC13838@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 23, 2016 at 01:36:57PM -0400, Tom Lane wrote:
> David Fetter <david(at)fetter(dot)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.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2016-05-23 17:47:36 | Re: Calling json_* functions with JSONB data |
Previous Message | Tom Lane | 2016-05-23 17:40:30 | Re: Parallel pg_dump's error reporting doesn't work worth squat |