| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Window Function "Run Conditions" |
| Date: | 2022-03-22 22:39:13 |
| Message-ID: | CAApHDvq29swVhJZAgLfVsrXHU-sFbEDePaCzWfauv5UvWu13KA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 17 Mar 2022 at 17:04, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> It seems like this effort would aid in implementing what some other databases implement via the QUALIFY clause, which is to window functions what HAVING is to aggregate functions.
> example: https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#qualify_clause
Isn't that just syntactic sugar? You could get the same from adding a
subquery where a WHERE clause to filter rows evaluated after the
window clause.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-22 22:41:45 | Re: New Object Access Type hooks |
| Previous Message | Mark Dilger | 2022-03-22 22:37:37 | Re: New Object Access Type hooks |