官术网_书友最值得收藏!

Utilizing windowing functions and analytics

After discussing ordered sets, it is time to take a look at windowing functions. Aggregates follow a fairly simple principle: take many rows and turn them into fewer, aggregated rows. A windowing function is different. It compares the current row with all rows in the group. The number of rows returned does not change.

Here is an example:

test=# SELECT avg(production) FROM t_oil; 
avg
-----------
2607.5139
(1 row)

test=# SELECT country, year, production, consumption, avg(production) OVER ()
FROM t_oil
LIMIT 4;
country | year | production | consumption | avg
---------+------+------------+-------------+----------
USA | 1965 | 9014 | 11522 | 2607.5139
USA | 1966 | 9579 | 12100 | 2607.5139
USA | 1967 | 10219 | 12567 | 2607.5139
USA | 1968 | 10600 | 13405 | 2607.5139
(4 rows)

The average production in our dataset is around 2.6 million barrels per day. The goal of this query is to add this value as a column. It is now easy to compare the current row to the overall average.

Keep in mind that the OVER clause is essential. PostgreSQL is not able to process the query without it:

test=# SELECT country, year, production, consumption, avg(production)  
FROM t_oil;
ERROR: column "t_oil.country" must appear in the GROUP BY clause or be used in an aggregate function
LINE 1: SELECT country, year, production, consumption, avg(productio...

This actually makes sense because the average has to be defined precisely. The database engine cannot just take any value, which might be right by doing guesswork.

Other database engines can accept aggregate functions without an  OVER or even a GROUP BY clause. However, from a logical point of view this is wrong and on top of that a violation of SQL.
主站蜘蛛池模板: 洞口县| 武宁县| 湖州市| 韶关市| 祁东县| 赞皇县| 滕州市| 鸡西市| 科技| 郴州市| 澳门| 清新县| 拜泉县| 丘北县| 古蔺县| 莱西市| 涪陵区| 平潭县| 同德县| 朝阳区| 凤城市| 霍林郭勒市| 苍山县| 六安市| 梁平县| 兴义市| 石首市| 宜宾市| 渑池县| 武义县| 义马市| 突泉县| 南城县| 宣恩县| 霍林郭勒市| 清河县| 垫江县| 昌图县| 盐津县| 达拉特旗| 兴山县|