What is the principle of oracle paging query
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.
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;
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
--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
--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;
--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;
--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
--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;
--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
--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;
--Decomposition steps
--The first step:
SELECT * FROM emp ORDER BY sal DESC
--The second step:
SELECT e .*,ROWNUM rn FROM (SELECT * FROM emp ORDER BY sal DESC) e
--The third step:
SELECT e .*,ROWNUM rn FROM (SELECT * FROM emp ORDER BY sal DESC) e WHERE ROWNUM<=10
--The fourth step:
SELECT * FROM( SELECT e .*,ROWNUM rn FROM (SELECT * FROM emp ORDER BY sal DESC) e WHERE ROWNUM<=10) WHERE rn>=5
--Wrong guess.
SELECT e .*,ROWNUM rn FROM (SELECT * FROM emp ORDER BY sal DESC) e WHERE rn<=10
--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
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!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



To query the Oracle tablespace size, follow the following steps: Determine the tablespace name by running the query: SELECT tablespace_name FROM dba_tablespaces; Query the tablespace size by running the query: SELECT sum(bytes) AS total_size, sum(bytes_free) AS available_space, sum(bytes) - sum(bytes_free) AS used_space FROM dba_data_files WHERE tablespace_

There are the following methods to get time in Oracle: CURRENT_TIMESTAMP: Returns the current system time, accurate to seconds. SYSTIMESTAMP: More accurate than CURRENT_TIMESTAMP, to nanoseconds. SYSDATE: Returns the current system date, excluding the time part. TO_CHAR(SYSDATE, 'YYY-MM-DD HH24:MI:SS'): Converts the current system date and time to a specific format. EXTRACT: Extracts a specific part from a time value, such as a year, month, or hour.

There are three ways to view instance names in Oracle: use the "sqlplus" and "select instance_name from v$instance;" commands on the command line. Use the "show instance_name;" command in SQL*Plus. Check environment variables (ORACLE_SID on Linux) through the operating system's Task Manager, Oracle Enterprise Manager, or through the operating system.

Oracle View Encryption allows you to encrypt data in the view, thereby enhancing the security of sensitive information. The steps include: 1) creating the master encryption key (MEk); 2) creating an encrypted view, specifying the view and MEk to be encrypted; 3) authorizing users to access the encrypted view. How encrypted views work: When a user querys for an encrypted view, Oracle uses MEk to decrypt data, ensuring that only authorized users can access readable data.

Uninstall method for Oracle installation failure: Close Oracle service, delete Oracle program files and registry keys, uninstall Oracle environment variables, and restart the computer. If the uninstall fails, you can uninstall manually using the Oracle Universal Uninstall Tool.

Oracle Invalid numeric errors may be caused by data type mismatch, numeric overflow, data conversion errors, or data corruption. Troubleshooting steps include checking data types, detecting digital overflows, checking data conversions, checking data corruption, and exploring other possible solutions such as configuring the NLS_NUMERIC_CHARACTERS parameter and enabling data verification logging.

To create a user in Oracle, follow these steps: Create a new user using the CREATE USER statement. Grant the necessary permissions using the GRANT statement. Optional: Use the RESOURCE statement to set the quota. Configure other options such as default roles and temporary tablespaces.

The method to solve the Oracle cursor closure problem includes: explicitly closing the cursor using the CLOSE statement. Declare the cursor in the FOR UPDATE clause so that it automatically closes after the scope is ended. Declare the cursor in the USING clause so that it automatically closes when the associated PL/SQL variable is closed. Use exception handling to ensure that the cursor is closed in any exception situation. Use the connection pool to automatically close the cursor. Disable automatic submission and delay cursor closing.
