| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| 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:36:57 |
| Message-ID: | 1199.1464025017@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-23 17:40:30 | Re: Parallel pg_dump's error reporting doesn't work worth squat |
| Previous Message | David Fetter | 2016-05-23 17:35:10 | Re: Changed SRF in targetlist handling |