From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | zzzzz(dot)graf(at)gmail(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15658: Window Function in a left join using AS or alias for the cloumn name |
Date: | 2019-02-26 22:56:26 |
Message-ID: | 15647.1551221786@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> I believe I found an obscure bug with the window function
Hm, could we see a self-contained example, ie with the underlying
table/view definitions too? Probably don't need any sample data
for this type of problem, but I'm unexcited about trying to reverse-
engineer your table definitions enough to reproduce the problem.
> The error occurs when I put the query into a LEFT JOIN:
> select counts.count,
> caldetail.*, calprorules_desired_value, calprorules_stdpreceision,
I'm wondering why this didn't already fail at "counts.count", because with
the "AS howmany" in place, that sub-select isn't returning any column
named "count". I kind of suspect user error due to ambiguous column
names, but the details aren't obvious.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin | 2019-02-27 01:15:41 | Re: BUG #15658: Window Function in a left join using AS or alias for the cloumn name |
Previous Message | PG Bug reporting form | 2019-02-26 18:55:59 | BUG #15658: Window Function in a left join using AS or alias for the cloumn name |