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

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.
主站蜘蛛池模板: 乌鲁木齐市| 泰兴市| 海宁市| 富阳市| 涞源县| 咸阳市| 微山县| 会泽县| 通化县| 抚远县| 定安县| 阿克| 新野县| 巴中市| 嘉义县| 百色市| 通江县| 新津县| 鄯善县| 黄石市| 察哈| 临汾市| 涪陵区| 读书| 腾冲县| 石棉县| 阳山县| 百色市| 吴忠市| 灌云县| 高州市| 如东县| 平罗县| 博白县| 五原县| 汽车| 宜良县| 嵊泗县| 金秀| 江阴市| 白银市|