Version sans cache

Mise en cache désactivé. Réglage défaut pour cette page : actif (code DEF204)
Si l'affichage est trop lent, vous pouvez désactiver le mode utilisateur pour visualiser la version en cache.

Rechercher dans le manuel MySQL

12.21.4 Named Windows

Table des matières

Windows can be defined and given names by which to refer to them in OVER clauses. To do this, use a WINDOW clause. If present in a query, the WINDOW clause falls between the positions of the HAVING and ORDER BY clauses, and has this syntax:

  1. WINDOW window_name AS (window_spec)
  2.     [, window_name AS (window_spec)] ...

For each window definition, window_name is the window name, and window_spec is the same type of window specification as given between the parentheses of an OVER clause, as described in Section 12.21.2, “Window Function Concepts and Syntax”:

  1. window_spec:
  2.     [window_name] [partition_clause] [order_clause] [frame_clause]

A WINDOW clause is useful for queries in which multiple OVER clauses would otherwise define the same window. Instead, you can define the window once, give it a name, and refer to the name in the OVER clauses. Consider this query, which defines the same window multiple times:

  1. SELECT
  2.   val,
  3.   ROW_NUMBER() OVER (ORDER BY val) AS 'row_number',
  4.   RANK()       OVER (ORDER BY val) AS 'rank',
  5.   DENSE_RANK() OVER (ORDER BY val) AS 'dense_rank'
  6. FROM numbers;

The query can be written more simply by using WINDOW to define the window once and referring to the window by name in the OVER clauses:

  1. SELECT
  2.   val,
  3.   ROW_NUMBER() OVER w AS 'row_number',
  4.   RANK()       OVER w AS 'rank',
  5.   DENSE_RANK() OVER w AS 'dense_rank'
  6. FROM numbers
  7. WINDOW w AS (ORDER BY val);

A named window also makes it easier to experiment with the window definition to see the effect on query results. You need only modify the window definition in the WINDOW clause, rather than multiple OVER clause definitions.

If an OVER clause uses OVER (window_name ...) rather than OVER window_name, the named window can be modified by the addition of other clauses. For example, this query defines a window that includes partitioning, and uses ORDER BY in the OVER clauses to modify the window in different ways:

  1. SELECT
  2.   DISTINCT year, country,
  3.   FIRST_VALUE(year) OVER (w ORDER BY year ASC) AS first,
  4.   FIRST_VALUE(year) OVER (w ORDER BY year DESC) AS last
  5. FROM sales
  6. WINDOW w AS (PARTITION BY country);

An OVER clause can only add properties to a named window, not modify them. If the named window definition includes a partitioning, ordering, or framing property, the OVER clause that refers to the window name cannot also include the same kind of property or an error occurs:

  • This construct is permitted because the window definition and the referring OVER clause do not contain the same kind of properties:

    1. OVER (w ORDER BY country)
    2. ... WINDOW w AS (PARTITION BY country)

  • This construct is not permitted because the OVER clause specifies PARTITION BY for a named window that already has PARTITION BY:

    1. OVER (w PARTITION BY year)
    2. ... WINDOW w AS (PARTITION BY country)

The definition of a named window can itself begin with a window_name. In such cases, forward and backward references are permitted, but not cycles:

  • This is permitted; it contains forward and backward references but no cycles:

    1. WINDOW w1 AS (w2), w2 AS (), w3 AS (w1)

  • This is not permitted because it contains a cycle:

    1. WINDOW w1 AS (w2), w2 AS (w3), w3 AS (w1)

Rechercher dans le manuel MySQL

Traduction non disponible

Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.

Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-window-functions-named-windows.html

L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.

Références

  1. Consulter le document html Langue du document :en Manuel MySQL : https://dev.mysql.com/

Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.

Table des matières Haut