Syntax for Oracle paging query statements (GO)

Paging queries are often used when working with database systems, and the following is a detailed introduction to the paging query statements in the Oracle database system for your reference.

Oracle Paging Query statements make one of our most commonly used statements , as described below, for the use of Oracle paging Query statements , and if you are interested in this aspect, you may wish to take a look.

Oracle Paging Query statements can basically be applied in the format given in this article.
Oracle Split-page query format:

SELECT * FROM (select A.*, ROWNUM rn from (SELECT * FROM table_name) A where ROWNUM <=) where RN >= 21;

The most internal query, select * FROM table_name, represents the original query statement without paging. ROWNUM <= 40 and RN >= 21 control the range of pages per page for paged queries.

This Oracle paged query statement given above is highly efficient in most cases. The purpose of paging is to control the output result set size and return the results as soon as possible. In the above paged query statement , this consideration is mainly reflected in the where ROWNUM <= 40 sentence.

There are two ways to select the 21st to 40th record, one of which is shown in the above example in the second layer of the query through the rownum <= 40来 control The maximum value, at the outermost level of the query control the minimum value. The other way is to remove the ROWNUM <= in the second layer of the query, controlling the minimum and maximum values of the paging at the outermost level of the query. The query statements are as follows:

SELECT * FROM (select A.*, ROWNUM rn from (SELECT * from table_name) A) WHERE RN between and 40;

In contrast to these two formulations, the first query is much more efficient than the second in most cases.

This is because in the CBO optimization mode, Oracle can push the outer query condition into the inner query to improve the execution efficiency of the inner query. For the first query statement , the second level of the query condition where ROWNUM <= 40 can be pushed into the inner query by Oracle, so that if the results of an Oracle query exceed the ROWNUM limit, the result is returned to the terminating query.

and the second query statement , because the query condition between and 40 is present in the third layer of the query, and Oracle cannot push the third layer of the query conditions to the most inner layer (even pushing to the inner layer is meaningless, because the most inner query does not know what RN represents). Therefore, for the second query statement , the Oracle's inner layer is returned to the middle tier as all data that satisfies the criteria, and the middle tier returns to the outermost of all the data. Data filtering is done at the outermost layer, and obviously this is much less efficient than the first query.

The query analyzed above is not just a simple query for a single table, but is as effective for the most inner query as a complex multi-table union query or a case in which the inner query contains a sort.

Syntax for Oracle paging query statements (GO)