ROWNUM
For each row returned by a query, the
ROWNUMpseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. The first row selected has aROWNUMof 1, the second has 2, and so on.You can use
ROWNUMto limit the number of rows returned by a query, as in this example:SELECT * FROM employees WHERE ROWNUM < 10;If an
ORDERBYclause followsROWNUMin the same query, then the rows will be reordered by theORDERBYclause. The results can vary depending on the way the rows are accessed. For example, if theORDERBYclause causes Oracle to use an index to access the data, then Oracle may retrieve the rows in a different order than without the index. Therefore, the following statement will not have the same effect as the preceding example:SELECT * FROM employees WHERE ROWNUM < 11 ORDER BY last_name;If you embed the
ORDERBYclause in a subquery and place theROWNUMcondition in the top-level query, then you can force theROWNUMcondition to be applied after the ordering of the rows. For example, the following query returns the employees with the 10 smallest employee numbers. This is sometimes referred to as top-N reporting:SELECT * FROM (SELECT * FROM employees ORDER BY employee_id) WHERE ROWNUM < 11;In the preceding example, the
ROWNUMvalues are those of the top-levelSELECTstatement, so they are generated after the rows have already been ordered byemployee_idin the subquery.Conditions testing for
ROWNUMvalues greater than a positive integer are always false. For example, this query returns no rows:SELECT * FROM employees WHERE ROWNUM > 1;The first row fetched is assigned a
ROWNUMof 1 and makes the condition false. The second row to be fetched is now the first row and is also assigned aROWNUMof 1 and makes the condition false. All rows subsequently fail to satisfy the condition, so no rows are returned.You can also use
ROWNUMto assign unique values to each row of a table, as in this example:UPDATE my_table SET column1 = ROWNUM;