Can I use… cycle … (Recursive Queries)

Apache DerbyBigQueryDb2 (LUW)H2MariaDBMySQLOracle DBPostgreSQLSQL ServerSQLite20052007200920112013201520172019202110.,bb
  1. Use cycle … restrict
  2. No using … sub-clause

The cycle clause monitors selected columns of the result of a recursive query for recurring values. If the same values appear a second time, the cycle clause prevents following that path a second time. Thereby the cycle clause prevents infinite loops.

WITH RECURSIVE path (a, b) AS (
  SELECT edges.* FROM edges
                WHERE a = 1
  SELECT edges.* FROM edges
                 JOIN path 
                   ON edges.a = path.b
  SET cycl TO 'Y' DEFAULT 'N'
USING path_array
  FROM path
 WHERE cycl = 'N'

Note that the result will have one row for each cycle twice. The cycl column defined in set can be used to drop the duplicates.

The cycle clause consists of three parts:

CYCLE <cycle column list>

List of columns for which a loop—and only a loop—causes recurring values.

SET <column name> [TO <value> DEFAULT <value>]

Adds a column to identify rows that were closing a cycle.

The optional to and default sub-clauses specify the values that mark rows processed before a cycle was closed (to) and those that were closing a cycle (default). If skipped it defaults to false default true.0

USING <column name>

Adds a column that contains an array with a list of steps that have led to each row.

The values in the array are row-values of the columns listed right after the cycle keyword.

Even though the SQL standard strictly requires the set and using sub-clauses, they are conceptually not required if the columns they define are not needed in the result. Some products do not support these sub-clauses at all. Note that skipping set has a logical impact: the duplicate rows cannot be filtered as shown in the where clause above. Therefore, skipping set may also imply not repeating the rows that close a cycle.

Normative References

The cycle clause is defined in ISO/IEC 9075:2016-2 as part of optional feature T131, “Recursive query”.

About the Author

Photo of Markus Winand

Markus Winand is the SQL Renaissance Ambassador. He is on a mission to introduce developers to the evolution of SQL in the 21st century. Markus can be hired as trainer, speaker and consultant via

Buy his Book on Amazon

Cover of “SQL Performance Explained”: Squirrel running on grass

The essence of SQL tuning in 200 pages

Buy on Amazon
(paperback only)

Paperback and PDF also available at Markus’ store.

Hire Markus

Markus offers SQL training and consulting for developers working at companies of any size.
Learn more »


  1. The to and default sub-clauses accept values of the types char(1) and boolean only.

Connect with Markus Winand

Markus Winand on LinkedInMarkus Winand on XINGMarkus Winand on Twitter
“modern SQL” by Markus Winand is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
Legal | Contact | NO WARRANTY | Trademarks | Privacy and GDPR | CC-BY-NC-ND 3.0 license