OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Database

SQL - V4.3.5

    Download PDF

    OceanBase logo

    The Unified Distributed Database for the AI Era.

    Follow Us
    Products
    OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
    Resources
    DocsBlogLive DemosTraining & CertificationTicket
    Company
    About OceanBaseTrust CenterLegalPartnerContact Us
    Follow Us

    © OceanBase 2026. All rights reserved

    Cloud Service AgreementPrivacy PolicySecurity
    Contact Us
    Document Feedback
    1. Documentation Center
    2. OceanBase Database
    3. SQL
    4. V4.3.5
    iconOceanBase Database
    SQL - V 4.3.5
    Databases
    • OceanBase Database
    • OceanBase Cloud
    • OceanBase Tugraph
    • Interactive Tutorials
    • OceanBase Best Practices
    Tools
    • OceanBase Cloud Platform
    • OceanBase Migration Service
    • OceanBase Developer Center
    • OceanBase Migration Assessment
    • OceanBase Admin Tool
    • OceanBase Loader and Dumper
    • OceanBase Deployer
    • Kubernetes operator for OceanBase
    • OceanBase Diagnostic Tool
    • OceanBase Binlog Service
    Connectors and Middleware
    • OceanBase Database Proxy
    • Embedded SQL in C for OceanBase
    • OceanBase Call Interface
    • OceanBase Connector/C
    • OceanBase Connector/J
    • OceanBase Connector/ODBC
    • OceanBase Connector/NET
    SQL
    KV
    • V 4.6.0
    • V 4.4.2
    • V 4.3.5
    • V 4.3.3
    • V 4.3.1
    • V 4.3.0
    • V 4.2.5
    • V 4.2.2
    • V 4.2.1
    • V 4.2.0
    • V 4.1.0
    • V 4.0.0
    • V 3.1.4 and earlier

    Subqueries

    Last Updated:2026-04-09 02:53:54  Updated
    Share
    What is on this page
    Overview
    Subquery types
    Scenarios
    Keywords in subqueries
    Examples
    Scalar subqueries with a SELECT clause
    Table subqueries with a FROM clause
    Subqueries with WHERE and HAVING clauses
    EXISTS and correlated subqueries

    folded

    Share

    A subquery is a query nested in an upper-layer query. The SQL language supports multi-level nested queries, which means that one subquery can be nested with other subqueries.

    Overview

    Subqueries can be contained in various clauses of SQL statements, such as SELECT, FROM, and WHERE. A subquery in the FROM clause of a SELECT statement is called an inner join view. You can nest any number of subqueries in an inner join view. A subquery in the WHERE clause of a SELECT statement is called a nested subquery.

    Subquery types

    Subqueries can be divided into the following types based on the row and column numbers in the result set.

    Subquery type
    Result set
    Clause
    Scalar subquery Single column and single row
    • SELECT
    • WHERE
    • HAVING
    Column subquery Single column and multiple rows
    • WHERE
    • HAVING
    Row subquery Multiple columns and multiple rows
    • WHERE
    • HAVING
    Table subquery Multiple rows and multiple columns
    • FROM
    • EXISTS

    Scenarios

    Subqueries are mainly used in the following scenarios:

    • Define a row set to be inserted into the specified table in the INSERT or CREATE TABLE statement.

    • Define a row set to be included in a view in the CREATE VIEW statement.

    • Define one or more values to be assigned to existing rows in the UPDATE statement.

    • Provide values for the WHERE, HAVING, or START WITH clause in the SELECT, UPDATE, or DELETE statement.

    Keywords in subqueries

    Subqueries can contain the following keywords: IN, ANY, SOME, and ALL.

    • The IN keyword is frequently used in a WHERE expression to query data in a specified range.

    • The ANY and SOME keywords can be used with operators such as =, >, >=, <, <=, and <> to query data equal to, greater than, greater than or equal to, less than, less than or equal to, or not equal to the specified data.

    • The ALL keyword can be used with operators such as =, >, >=, <, <=, and <> to specify values that are equal to, greater than, greater than or equal to, less than, less than or equal to, or not equal to all the specified data.

      Notice

      If the NOT IN keyword is used, and the column value in a subquery is NULL, the result of the outer query is empty.

    Examples

    Create tables named emp and dept and insert proper data into the tables.

    CREATE TABLE dept(  
        deptno           NUMBER(2,0),  
        dname            VARCHAR(14),  
        location         VARCHAR(13),   
        CONSTRAINT pk_dept PRIMARY KEY(deptno)  
    );
    
    INSERT INTO dept VALUES (20,'ACCOUNTING','Los Angeles');
    INSERT INTO dept VALUES (30,'OPERATIONS','CHICAGO');
    INSERT INTO dept VALUES (40,'SALES','NEW YORK');
    
    CREATE TABLE emp(  
        empno         NUMBER(4,0),  
        empname       VARCHAR(10),  
        job           VARCHAR(9),  
        mgr           NUMBER(4,0),  
        hiredate      DATE,  
        sal           NUMBER(7,2),  
        comm          NUMBER(7,2),        
        deptno        NUMBER(2,0),   
        CONSTRAINT PK_emp PRIMARY KEY (empno),
        CONSTRAINT FK_deptno  FOREIGN KEY (deptno)  REFERENCES dept (deptno)  
    );
    
    INSERT INTO emp VALUES (1698,'BLAKE','MANAGER',1839,'1981-5-1',2850,null,30);
    INSERT INTO emp VALUES (1566,'JONES','MANAGER',1839, '1981-4-2',2975,null,40);
    INSERT INTO emp VALUES (1788,'SCOTT','ANALYST',1566, '1987-7-15',3000,null,20);
    INSERT INTO emp VALUES (1902,'FORD','ANALYST',1566, '1981-12-5',3000,null,40);
    INSERT INTO emp VALUES (1369,'SMITH','CLERK',1902, '1980-12-17',800,null,20);
    INSERT INTO emp VALUES (1499,'ALLEN','SALESMAN',1698, '1981-2-20',1600,300,30);
    
    CREATE TABLE job_grades
    (
         grade_level VARCHAR(5),
         lowest_sal INT,
         highest_sal INT);
    
    INSERT INTO job_grades VALUE ('A', 1000, 1999);
    INSERT INTO job_grades VALUE ('B', 2000, 2999);
    INSERT INTO job_grades VALUE ('C', 3000, 3999);
    INSERT INTO job_grades VALUE ('D', 40000, 4999);
    INSERT INTO job_grades VALUE ('E', 5000, 5999);
    

    Scalar subqueries with a SELECT clause

    obclient> SELECT a.*,(SELECT count(*) FROM emp b WHERE b.deptno = a.deptno) AS Number of employees FROM dept a;
    +--------+------------+-------------+---------------------+
    | deptno | dname      | location    | Number of employees |
    +--------+------------+-------------+---------------------+
    |     20 | ACCOUNTING | Los Angeles |                   2 |
    |     30 | OPERATIONS | CHICAGO     |                   2 |
    |     40 | SALES      | NEW YORK    |                   2 |
    +--------+------------+-------------+---------------------+
    3 rows in set
    
    obclient> SELECT (SELECT a.dname FROM dept a, emp b WHERE a.deptno = b.deptno AND b.empno = 1566) AS Department name;
    +--------------+
    | Department name      |
    +--------------+
    | SALES        |
    +--------------+
    1 row in set
    

    Table subqueries with a FROM clause

    Use the result set of a subquery as a table and give an alias to the table. For example, the aliases of the tables in the following sample code are t1 and t2.

    obclient> SELECT t1.deptno,sa AS 'Average salary', t2.grade_level FROM (SELECT deptno,avg(a.sal) sa FROM emp a GROUP BY a.deptno) t1, job_grades t2 WHERE t1.sa BETWEEN t2.lowest_sal AND t2.highest_sal;
    +--------+----------------+-------------+
    | deptno | Average salary | grade_level |
    +--------+----------------+-------------+
    |     20 |    1900.000000 | A           |
    |     30 |    2225.000000 | B           |
    |     40 |    2987.500000 | B           |
    +--------+----------------+-------------+
    3 rows in set
    

    Subqueries with WHERE and HAVING clauses

    • Scalar subqueries

      /*Query the IDs of departments whose minimum salary is greater than that of No.30 department and their minimum salaries.*/
      obclient> SELECT min(a.sal) minsalary,deptno FROM emp a GROUP BY a.deptno HAVING min(a.sal) > (SELECT min(sal) FROM emp WHERE deptno = 30);
      +-----------+--------+
      | minsalary | deptno |
      +-----------+--------+
      |   2975.00 |     40 |
      +-----------+--------+
      1 row in set
      
    • Column subqueries that return a result set with one column and multiple rows

      /*Return the employee ID, employee name, job, and salary of the employees whose total salary is lower than that of the manager.*/
      
      obclient> SELECT empname Employee name, empno Employee ID, job Job title, sal Salary FROM emp WHERE sal < ALL (SELECT DISTINCT sal
      FROM emp WHERE job = 'MANAGER') AND job!= 'MANAGER';
      +---------------+-------------+-----------+---------+
      | Employee name | Employee ID | Job title | Salary  |
      +---------------+-------------+-----------+---------+
      | SMITH         |        1369 | CLERK     |  800.00 |
      | ALLEN         |        1499 | SALESMAN  | 1600.00 |
      +---------------+-------------+-----------+---------+
      2 rows in set
      
      obclient> SELECT empname Employee name, empno Employee ID, job Job title, sal Salary FROM emp WHERE sal < ALL (SELECT min(sal)
          FROM emp WHERE job = 'MANAGER') AND job!= 'MANAGER';
      +---------------+-------------+-----------+---------+
      | Employee name | Employee ID | Job title | Salary  |
      +---------------+-------------+-----------+---------+
      | SMITH         |        1369 | CLERK     |  800.00 |
      | ALLEN         |        1499 | SALESMAN  | 1600.00 |
      +---------------+-------------+-----------+---------+
      2 rows in set
      
    • Row subqueries that return a result set with one row and multiple columns

      obclient> SELECT * FROM emp a WHERE a.empno = (SELECT max(empno) FROM emp) AND sal = (SELECT max(sal) FROM emp);
      +-------+---------+---------+------+------------+---------+------+--------+
      | empno | empname | job     | mgr  | hiredate   | sal     | comm | deptno |
      +-------+---------+---------+------+------------+---------+------+--------+
      |  1902 | FORD    | ANALYST | 1566 | 1981-12-05 | 3000.00 | NULL |     40 |
      +-------+---------+---------+------+------------+---------+------+--------+
      1 row in set
      

    EXISTS and correlated subqueries

    In an EXISTS subquery, the main query is first executed to obtain a result, and then the result is filtered based on the conditions in the subquery. The subquery contains the fields that are used in the main query. Therefore, the subquery is called a correlated subquery. The query result of EXISTS is 1 or 0, which indicates whether the result set of the subquery contains values. In most cases, an EXISTS subquery can be replaced with an IN clause.

    Here is an example:

    obclient> SELECT exists(SELECT empno FROM emp WHERE sal = 3000) AS 'EXISTS returns 1 or 0';
    +----------------------+
    | EXISTS returns 1 or 0     |
    +----------------------+
    |                    1 |
    +----------------------+
    1 row in set
    
    obclient> SELECT dname FROM dept a WHERE exists(SELECT 1 FROM emp b WHERE a.deptno = b.deptno);
    +------------+
    | dname      |
    +------------+
    | ACCOUNTING |
    | OPERATIONS |
    | SALES      |
    +------------+
    3 rows in set
    
    obclient> SELECT dname FROM dept a WHERE a.deptno IN (SELECT deptno FROM emp);
    +------------+
    | dname      |
    +------------+
    | ACCOUNTING |
    | OPERATIONS |
    | SALES      |
    +------------+
    3 rows in set
    

    Previous topic

    RIGHT JOIN queries
    Last

    Next topic

    Lateral derived table
    Next
    What is on this page
    Overview
    Subquery types
    Scenarios
    Keywords in subqueries
    Examples
    Scalar subqueries with a SELECT clause
    Table subqueries with a FROM clause
    Subqueries with WHERE and HAVING clauses
    EXISTS and correlated subqueries