[ existing_window_name ]
[ PARTITION BY expression [, ...] ]
[ ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST | LAST } ] [, ...] ]
-[ framing_clause ]
+[ frame_clause ]
as well as its ordering clause if any. In this case the new window cannot
specify its own PARTITION BY> clause, and it can specify
ORDER BY> only if the copied window does not have one.
- The framing clause is never copied from the existing window.
+ The new window always uses its own frame clause; the copied window
+ must not specify a frame clause.
- The optional framing_clause> defines
+ The optional frame_clause> defines
the window frame> for window functions that depend on the
frame (not all do). It can be one of
The SQL standard provides additional options for the window
- framing_clause>.
+ frame_clause>.
PostgreSQL currently supports only the
options listed above.
-
+
SQL Syntax
where window_definition
has the syntax
-[ window_name ]
+[ existing_window_name ]
[ PARTITION BY expression [, ...] ]
[ ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST | LAST } ] [, ...] ]
-[ framing_clause ]
+[ frame_clause ]
- and the optional framing_clause
+ and the optional frame_clause
can be one of
RANGE UNBOUNDED PRECEDING
Named window specifications are usually referenced with just
OVER> window_name, but it is
also possible to write a window name inside the parentheses and then
- optionally override its ordering clause and/or framing clause.
+ optionally supply an ordering clause and/or frame clause (the referenced
+ window must lack these clauses, if they are supplied here).
This latter syntax follows the same rules as modifying an existing
window name within the WINDOW clause; see the
reference
+ The frame_clause specifies
+ the set of rows constituting the window frame>, for those
+ window functions that act on the frame instead of the whole partition.
The default framing option is RANGE UNBOUNDED PRECEDING>,
which is the same as RANGE BETWEEN UNBOUNDED PRECEDING AND
CURRENT ROW>; it selects rows up through the current row's last
The built-in window functions are described in
- linkend="functions-window-table">. Also, any built-in or
- user-defined aggregate function can be used as a window function.
+ linkend="functions-window-table">. Other window functions can be added by
+ the user. Also, any built-in or user-defined aggregate function can be
+ used as a window function.
*
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/parser/parse_clause.c,v 1.183 2008/12/31 00:08:37 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/parser/parse_clause.c,v 1.184 2008/12/31 23:42:56 tgl Exp $
*
*-------------------------------------------------------------------------
*/
* Per spec, a windowdef that references a previous one copies the
* previous partition clause (and mustn't specify its own). It can
* specify its own ordering clause. but only if the previous one
- * had none. It always specifies its own framing clause.
+ * had none. It always specifies its own frame clause, and the
+ * previous one must not have a frame clause. (Yeah, it's bizarre
+ * that each of these cases works differently, but SQL:2008 says so;
+ * see 7.11 syntax rule 10 and general rule 1.)
*/
if (refwc)
{
wc->orderClause = orderClause;
wc->copiedOrder = false;
}
+ if (refwc && refwc->frameOptions != FRAMEOPTION_DEFAULTS)
+ ereport(ERROR,
+ (errcode(ERRCODE_WINDOWING_ERROR),
+ errmsg("cannot override frame clause of window \"%s\"",
+ windef->refname),
+ parser_errposition(pstate, windef->location)));
wc->frameOptions = windef->frameOptions;
wc->winref = winref;