Window function (SQL)
In SQL, a window function or analytic function[1] is a function which uses values from one or multiple rows to return a value for each row. (This contrasts with an aggregate function, which returns a single value for multiple rows.) Window functions have an OVER clause; any function without an OVER clause is not a window function, but rather an aggregate or single-row (scalar) function.[2]
As an example, here is a query which uses a window function to compare each employee with the average salary of their department (example from the PostgreSQL documentation):[3]
SELECT depname, empno, salary, avg(salary) OVER (PARTITION BY depname) FROM empsalary;
Output:
depname | empno | salary | avg
-----------+-------+--------+-----------------------
develop | 11 | 5200 | 5020.0000000000000000
develop | 7 | 4200 | 5020.0000000000000000
develop | 9 | 4500 | 5020.0000000000000000
develop | 8 | 6000 | 5020.0000000000000000
develop | 10 | 5200 | 5020.0000000000000000
personnel | 5 | 3500 | 3700.0000000000000000
personnel | 2 | 3900 | 3700.0000000000000000
sales | 3 | 4800 | 4866.6666666666666667
sales | 1 | 5000 | 4866.6666666666666667
sales | 4 | 4800 | 4866.6666666666666667
(10 rows)
The PARTITION BY
clause groups rows into partitions, and the function is applied to each partition separately. If the PARTITION BY
clause is omitted (such as if we have an empty OVER()
clause), then the entire result set treated as a single partition.[4] For this query, the average salary reported would be the average taken over all rows.
Window functions are evaluated after aggregation (after the GROUP BY
clause and non-window aggregate functions, for example).[1]
Syntax
According to the PostgreSQL documentation, a window function has the syntax of one of the following:[4]
function_name ([expression [, expression ... ]]) OVER window_name
function_name ([expression [, expression ... ]]) OVER ( window_definition )
function_name ( * ) OVER window_name
function_name ( * ) OVER ( window_definition )
where window_definition
has syntax:
[ existing_window_name ]
[ PARTITION BY expression [, ...] ]
[ ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST | LAST } ] [, ...] ]
[ frame_clause ]
frame_clause
has the syntax of one of the following:
{ RANGE | ROWS | GROUPS } frame_start [ frame_exclusion ]
{ RANGE | ROWS | GROUPS } BETWEEN frame_start AND frame_end [ frame_exclusion ]
frame_start
and frame_end
can be UNBOUNDED PRECEDING
, offset PRECEDING
, CURRENT ROW
, offset FOLLOWING
, or UNBOUNDED FOLLOWING
. frame_exclusion
can be EXCLUDE CURRENT ROW
, EXCLUDE GROUP
, EXCLUDE TIES
, or EXCLUDE NO OTHERS
.
expression
refers to any expression that does not contain a call to a window function.
Notation:
- Brackets [] indicate optional clauses
- Curly braces {} indicate a set of different possible options, with each option delimited by a vertical bar |
Window frame
![]() | This section is empty. You can help by adding to it. (March 2021) |
History
Window functions were introduced in SQL:2003 and had functionality expanded in later specifications.[5]
See also
References
- ^ a b "Analytic function concepts in Standard SQL | BigQuery". Google Cloud. Retrieved 2021-03-23.
- ^ "Window Functions". sqlite.org. Retrieved 2021-03-23.
- ^ "3.5. Window Functions". PostgreSQL Documentation. 2021-02-11. Retrieved 2021-03-23.
- ^ a b "4.2. Value Expressions". PostgreSQL Documentation. 2021-02-11. Retrieved 2021-03-23.
- ^ "Window Functions Overview". MariaDB KnowledgeBase. Retrieved 2021-03-23.