Home > Database > Oracle > What is the principle of oracle paging query

What is the principle of oracle paging query

WBOY
Release: 2022-01-25 16:59:31
Original
5302 people have browsed it

Oracle's paging query principle: 1. Use the characteristics of ORACLE's rownum field to query; 2. Query the specified number of N pieces of data; 3. Remove the M pieces of data from the specified number of N pieces of query results; 4. In web development, by passing M and N as parameters, you can get paginated results.

What is the principle of oracle paging query

The operating environment of this tutorial: Windows 10 system, Oracle 11g version, Dell G3 computer.

What is the principle of oracle paging query?

The principle of paging:

1. Use the characteristics of the rownum field of ORACLE to query.

2. Query the first N pieces of data

3. Get M to N pieces of data from the query results in step 2

4. In web development Pass M and N as parameters to get paginated results.

Example: Query 20~30 records in the table, the sql statement is as follows.

select *   from( 
 select   rownum  as  pageNo,  A.*   from    tableName     A   where   rownum   <=   30)  B  where B.pageNo >=20;
Copy after login

Example:

--How to get the top 5 highest paid people in the employee table?

SELECT * FROM(
SELECT * FROM emp ORDER BY sal DESC)
WHERE Rownum<6
Copy after login

--How to obtain the information of the employee whose salary is ranked 5th in the employee table

SELECT * FROM(
SELECT * FROM emp ORDER BY sal DESC)
WHERE Rownum=5
Copy after login

--No content can be found in the query

--Same ROWNUM>=5 query 5 The results after the first place also failed

--This involves ROWNUM, which can only be less than but not greater than or equal to. So--an important obstacle to paging queries in Oracle database is this.

--As for the principle, ROWNUM is a pseudo column that must be arranged starting from 1 every time. So ROWNUM>=n. For example, it is not true if 1 is greater than any n (number of items). It can be found with ROWNUM=1. Because 1>=1 holds. N=2,1>=2 is not true. Therefore, only the first item can be checked for greater than or equal to. Plus less than or equal to. That’s all I can check. Therefore, this difficulty can be regarded as increasing the difficulty and obstacles of paging query.

--Method 1 The simplest query

--Articles 5 to 10.

--There is only one layer of nesting and one subquery,

SELECT * FROM
(SELECT ROWNUM rn ,e.* FROM emp e WHERE ROWNUM<=10)
WHERE rn>=5;
Copy after login

--This is actually transformed from the following method.

--That is, the new table obtained by the subquery is queried again.

--The key step is ROWNUM rn.

--And don't forget e.*, otherwise there will be no complete data.

SELECT * FROM (SELECT ROWNUM rn, e.*
          FROM emp e
         WHERE ROWNUM <= 10) table_1
 WHERE table_1.rn>= 5;
Copy after login

--The above is not sorted, the following is sorted

--Because it must be sorted first before querying, the larger the table, the slower the efficiency.

--Method 2

SELECT * FROM
(SELECT ROWNUM rm ,e.* FROM emp e order by sal DESC )
WHERE rm>=5 AND rm<=10
Copy after login

--The following is the method of using analytical functions;

--Method 3

SELECT * 
FROM (SELECT emp.*,
   ROW_NUMBER () OVER (ORDER BY sal DESC) rank 
    FROM emp)   
WHERE rank >=6 AND rank<=10;
Copy after login

--But our actual query Looking at the results, it turns out they are completely different.

--Checked manually. The results of the analytical function method are correct. Don't understand.

--Can anyone explain it?

--Here comes a meaningless

SELECT * FROM 
(SELECT e.*, ROWNUM AS rn from 
( SELECT * FROM emp ORDER BY sal DESC) e
)ee 
WHERE ee.rn>=5 AND ee.rn<=10
Copy after login

--Method 4 (massive data query, such as Baidu, Tmall query)

SELECT * FROM(
SELECT e.* ,ROWNUM rn
FROM (
SELECT *
FROM emp
ORDER BY sal DESC
) e
WHERE  ROWNUM<=10
)WHERE rn>=6;
Copy after login

--Decomposition steps

--The first step:

SELECT * FROM emp ORDER BY sal DESC
Copy after login

--The second step:

SELECT e .*,ROWNUM rn FROM
(SELECT * FROM emp ORDER BY sal DESC) e
Copy after login

--The third step:

SELECT e .*,ROWNUM rn FROM
(SELECT * FROM emp ORDER BY sal DESC) e
WHERE ROWNUM<=10
Copy after login

--The fourth step:

SELECT * FROM(
SELECT e .*,ROWNUM rn FROM
(SELECT * FROM emp ORDER BY sal DESC) e
WHERE ROWNUM<=10)
WHERE rn>=5
Copy after login

--Wrong guess.

SELECT e .*,ROWNUM rn FROM
(SELECT * FROM emp ORDER BY sal DESC) e
WHERE rn<=10
Copy after login

--To create an alias, you must query the data table.

--The query conditions are judged by conditions that do not yet exist, so they naturally fail.

--Method five, idle and boring usage

WITH ee AS (
  SELECT e.*, ROWNUM rn FROM
 ( SELECT * FROM emp ORDER BY sal DESC )e
  )
  SELECT ee.*
  FROM ee
  WHERE ee.rn>=5 AND ee.rn<=10
Copy after login

Recommended tutorial: "Oracle Video Tutorial"

The above is the detailed content of What is the principle of oracle paging query. For more information, please follow other related articles on the PHP Chinese website!

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template