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.4.2

    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.4.2
    iconOceanBase Database
    SQL - V 4.4.2
    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

    MATCH AGAINST

    Last Updated:2026-04-02 06:23:57  Updated
    share
    What is on this page
    Purpose
    Syntax
    Parameters
    mode_flag
    Considerations
    Execution method of text retrieval
    Examples
    Example of text retrieval execution plan
    References

    folded

    share

    Purpose

    This expression is used for text retrieval on a full-text index. The AGAINST clause accepts a search string and searches the index based on the collation. For each row in the table, the return value of MATCH represents the relevance between the search string and the data in the row, i.e., the similarity between the text in the search string and the text in the data table.

    Syntax

    MATCH (column_set) AGAINST (query_expr [mode_flag])
    
    column_set:
        column_name [, column_name ...]
    
    mode_flag:
        IN NATURAL LANGUAGE MODE
        | IN BOOLEAN MODE
        | IN MATCH PHRASE MODE
    

    Parameters

    Field
    Description
    column_set Specifies the column to be searched. If multiple columns are specified, they must be separated by commas. The query is independent of the order of the columns. To execute the MATCH AGAINST expression, there must be a full-text index that exactly matches the column_set.
    query_expr Specifies the keyword or phrase to be searched, which is the parameter to be matched. OceanBase Database will tokenize query_expr using the tokenizer of the full-text index and then perform a search on the full-text index.
    mode_flag Optional. Specifies the search mode. The default value is IN NATURAL LANGUAGE MODE. For more information, see mode_flag.

    mode_flag

    • IN NATURAL LANGUAGE MODE: The default value. Specifies to use the natural language search mode. In this mode, the full-text search is performed by tokenizing the query expression (query_expr) to obtain a set of tokens (token) and matching these tokens with those in the index. A match is considered successful if at least one token matches. The relevance of the matched rows is ranked using the Okapi BM25 method.

      By default, or if IN NATURAL LANGUAGE MODE is specified, MATCH AGAINST will use the NATURAL LANGUAGE mode for full-text search. In this mode, AGAINST accepts a search string and searches the index based on the collation. For each row in the table, the return value of MATCH represents the relevance between the search string and the data in the row, i.e., the similarity between the text in the search string and the text in the data table.

    • IN BOOLEAN MODE: Specifies to use the Boolean search mode. This mode supports three commonly used Boolean operators and nested operations, as follows:

      • +: Represents AND, which is the intersection.

      • -: Represents the negation, which is the difference.

      • No operator: When used alone, it represents OR, which is the union. For example, A B means A OR B. Using the operator with the symbol will increase the relevance of the sentence but will lose the OR semantics. For example, +A B means that A must be present, and the relevance between A and B in the sentence is calculated.

      • (): Represents nested operations. If there is no symbol outside the parentheses, it has the OR semantics. For example, +A (nested clause) means that A must be present or the nested clause must be present.

        Note

        For OceanBase Database V4.3.5, support for IN BOOLEAN MODE was introduced starting from V4.3.5 BP1.

        Here are some examples:

        1. Output sentences must contain the word "computer".

          SELECT * FROM my_table WHERE MATCH (doc) AGAINST ("+computer" IN BOOLEAN MODE);
          
        2. Output sentences must contain the word "computer" and must not contain the word "weather".

          SELECT * FROM my_table WHERE MATCH (doc) AGAINST ("+computer -weather" IN BOOLEAN MODE);
          
        3. Output sentences must contain the word "computer", and those containing "oceanbase" are more relevant.

          SELECT * FROM my_table WHERE MATCH (doc) AGAINST ("+computer oceanbase" IN BOOLEAN MODE);
          
    • IN MATCH PHRASE MODE: Supports exact phrase matching.

      Note

      For OceanBase Database V4.4.0 and later, support for IN MATCH PHRASE MODE is available.

      Here are some examples:

      1. Create a table named test and add a full-text index to the specified column.

        CREATE TABLE test(c1 int, c2 VARCHAR(200), c3 TEXT, FULLTEXT INDEX fts_idx (c2, c3));
        
      2. Query records in the c2 and c3 columns that exactly match some words.

        SELECT c2 FROM test WHERE MATCH(c2,c3) AGAINST('some words' IN MATCH PHRASE MODE);
        

    Considerations

    The MATCH AGAINST expression, in addition to indicating text matching, contains other semantics when it appears in different clauses of SQL:

    • Projection of relevance:

      • Full-text search supports ranking based on term frequency, which can be represented by the projection of relevance through the MATCH AGAINST expression.
      • Relevance indicates the degree of match between the matched data rows and the query (Query) in MATCH AGAINST.
      • Relevance is a DOUBLE type data greater than or equal to 0. A value of 0 indicates that the data row is unrelated to the query (Query), and a higher value indicates a stronger relevance.
    • Filtering semantics:

      • When the MATCH AGAINST expression appears in the WHERE clause and is connected to all other filtering conditions using AND, it contains filtering semantics, indicating that it will filter out data rows that do not match.

        Example:

        SELECT id, digest, detail
        FROM t1
        WHERE MATCH (detail) AGAINST ('oceanbase');
        

        Equivalent to:

        SELECT id, digest, detail
        FROM t1
        WHERE MATCH (detail) AGAINST ('oceanbase') > 0;
        
    • Sorting semantics:

      • When the MATCH AGAINST expression appears in the WHERE clause and is connected to other filtering conditions using AND, it contains sorting semantics.
      • It indicates that the results of the full-text search will be sorted in descending order based on the relevance ranking of the MATCH AGAINST expression.
      • When there are multiple MATCH AGAINST expressions, the sorting will be based on the relevance of the first MATCH AGAINST expression.

      Example:

      SELECT id, digest, MATCH (detail) AGAINST ('oceanbase') AS relevance
      FROM t1
      WHERE MATCH (detail) against ('oceanbase');
      

      Equivalent to:

      SELECT id, digest, MATCH (detail) AGAINST ('oceanbase') AS relevance
      FROM t1
      WHERE MATCH (detail) AGAINST ('oceanbase')
      ORDER BY relevance DESC;
      

    Execution method of text retrieval

    • When the MATCH AGAINST expression contains filtering semantics in the SQL statement, OceanBase Database can execute the query by scanning the full-text index to calculate the MATCH AGAINST expression and then accessing the table.

    • When the MATCH AGAINST expression does not contain filtering semantics in the SQL statement, OceanBase Database supports scanning and filtering using other secondary indexes and accessing the full-text index based on the primary key to calculate the MATCH AGAINST expression.

    • When the WHERE clause of the SQL statement contains MATCH AGAINST and multiple filtering conditions connected by AND, and other secondary indexes can be hit, OceanBase Database will try to select the most cost-effective index for scanning.

    • When calculating the MATCH AGAINST expression by scanning the full-text index, if the query contains LIMIT, OceanBase Database will try to push the top-k calculation down to the full-text index scan to improve performance.

    • When the query contains MATCH AGAINST predicates connected by OR, an Index Merge plan will be automatically generated. Whether to choose the Index Merge plan depends on the cost competition result.

      Note

      • Starting from V4.4.1, the Index Merge plan supports multiple predicates connected by AND. When the query contains multiple predicates, including MATCH AGAINST, an Index Merge plan will be automatically generated.
      • In versions earlier than V4.4.1, the Index Merge plan only supports multiple predicates connected by OR.

    Examples

    1. Create the sample table test_tbl1, and create the full-text indexes ft_idx1_test_tbl1 and ft_idx1_test_tbl1, and the index idx_test_tbl1.

      CREATE TABLE test_tbl1(id INT, ref_no INT, digest VARCHAR(512), detail VARCHAR(4096),
          FULLTEXT INDEX ft_idx1_test_tbl1(detail),
          FULLTEXT INDEX ft_idx2_test_tbl1(digest, detail),
          INDEX idx_test_tbl1 (id));
      
    2. Insert test data into the test_tbl1 table.

      INSERT INTO test_tbl1 VALUES
          (1, 1234, 'fulltext', 'Try text retrieval with OceanBase fulltext index'),
          (2, 2345, 'log', 'OceanBase can halp with log analysis'),
          (3, 3456, 'order', 'Simple text retrieval scan will return result set in order of descending ranking in OceanBase'),
          (4, 4567, 'ranking', 'OceanBase will ranking relevance to query for matched result set'),
          (5, 5678, 'filter', 'Using text retrieval as a filter condition would be probably more efficient');
      
    3. Project relevance using the MATCH AGAINST expression.

      SELECT id, digest, detail, MATCH (detail) AGAINST ('oceanbase') AS relevance
      FROM test_tbl1;
      

      The returned result is as follows:

      +------+----------+-----------------------------------------------------------------------------------------------+--------------------+
      | id   | digest   | detail                                                                                        | relevance          |
      +------+----------+-----------------------------------------------------------------------------------------------+--------------------+
      |    1 | fulltext | Try text retrieval with OceanBase fulltext index                                              | 0.2989130434782609 |
      |    2 | log      | OceanBase can halp with log analysis                                                          | 0.3142857142857143 |
      |    3 | order    | Simple text retrieval scan will return result set in order of descending ranking in OceanBase |  0.240174672489083 |
      |    4 | ranking  | OceanBase will ranking relevance to query for matched result set                              | 0.2849740932642488 |
      |    5 | filter   | Using text retrieval as a filter condition would be probably more efficient                   |                  0 |
      +------+----------+-----------------------------------------------------------------------------------------------+--------------------+
      5 rows in set
      
    4. Filter using the MATCH AGAINST expression.

      SELECT id, digest, detail
      FROM test_tbl1
      WHERE MATCH (detail) AGAINST ('oceanbase');
      

      The returned result is as follows:

      +------+----------+-----------------------------------------------------------------------------------------------+
      | id   | digest   | detail                                                                                        |
      +------+----------+-----------------------------------------------------------------------------------------------+
      |    2 | log      | OceanBase can halp with log analysis                                                          |
      |    1 | fulltext | Try text retrieval with OceanBase fulltext index                                              |
      |    4 | ranking  | OceanBase will ranking relevance to query for matched result set                              |
      |    3 | order    | Simple text retrieval scan will return result set in order of descending ranking in OceanBase |
      +------+----------+-----------------------------------------------------------------------------------------------+
      4 rows in set
      
    5. Retrieve and sort using the MATCH AGAINST expression.

      SELECT id, digest, MATCH (detail) AGAINST ('oceanbase') AS relevance
      FROM test_tbl1
      WHERE MATCH (detail) AGAINST ('oceanbase');
      

      or

      SELECT id, digest, MATCH (detail) AGAINST ('oceanbase') AS relevance
      FROM test_tbl1
      WHERE MATCH (detail) AGAINST ('oceanbase')
      ORDER BY relevance DESC;
      

      The returned result is as follows:

      +------+----------+--------------------+
      | id   | digest   | relevance          |
      +------+----------+--------------------+
      |    2 | log      | 0.3142857142857143 |
      |    1 | fulltext | 0.2989130434782609 |
      |    4 | ranking  | 0.2849740932642488 |
      |    3 | order    |  0.240174672489083 |
      +------+----------+--------------------+
      4 rows in set
      

    Example of text retrieval execution plan

    1. The MATCH AGAINST expression contains filtering semantics and scans the full-text index ft_idx1_test_tbl1.

      EXPLAIN SELECT id, digest, detail
              FROM test_tbl1
              WHERE MATCH (detail) AGAINST ('oceanbase')
                  AND id = 3;
      

      The returned result is as follows:

      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      | Query Plan                                                                                                                                                  |
      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      | =============================================================================                                                                               |
      | |ID|OPERATOR             |NAME                        |EST.ROWS|EST.TIME(us)|                                                                               |
      | -----------------------------------------------------------------------------                                                                               |
      | |0 |SORT                 |                            |1       |30          |                                                                               |
      | |1 |└─TEXT RETRIEVAL SCAN|test_tbl1(ft_idx1_test_tbl1)|1       |30          |                                                                               |
      | =============================================================================                                                                               |
      | Outputs & filters:                                                                                                                                          |
      | -------------------------------------                                                                                                                       |
      |   0 - output([test_tbl1.id], [test_tbl1.digest], [test_tbl1.detail]), filter(nil), rowset=16                                                                |
      |       sort_keys([MATCH(test_tbl1.detail) AGAINST('oceanbase'), DESC])                                                                                       |
      |   1 - output([test_tbl1.detail], [test_tbl1.id], [test_tbl1.digest], [MATCH(test_tbl1.detail) AGAINST('oceanbase')]), filter([test_tbl1.id = 3]), rowset=16 |
      |       access([test_tbl1.__pk_increment], [test_tbl1.detail], [test_tbl1.id], [test_tbl1.digest]), partitions(p0)                                            |
      |       is_index_back=true, is_global_index=false, filter_before_indexback[false],                                                                            |
      |       calc_relevance=true, match_expr(MATCH(test_tbl1.detail) AGAINST('oceanbase')),                                                                        |
      |       pushdown_match_filter(MATCH(test_tbl1.detail) AGAINST('oceanbase'))                                                                                   |
      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      15 rows in set
      
    2. The MATCH AGAINST expression contains filtering semantics, but the ordinary secondary index idx_test_tbl1 is hit, and the cost of scanning the idx_test_tbl1 index is lower. Therefore, the idx_test_tbl1 index is scanned.

      EXPLAIN SELECT id
              FROM test_tbl1
              WHERE MATCH (detail) AGAINST ('oceanbase simple text retreival scan on fulltext index')
                  AND id = 3;
      

      The returned result is as follows:

      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      | Query Plan                                                                                                                                                  |
      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      | ======================================================================                                                                                      |
      | |ID|OPERATOR          |NAME                    |EST.ROWS|EST.TIME(us)|                                                                                      |
      | ----------------------------------------------------------------------                                                                                      |
      | |0 |SORT              |                        |1       |103         |                                                                                      |
      | |1 |└─TABLE RANGE SCAN|test_tbl1(idx_test_tbl1)|1       |103         |                                                                                      |
      | ======================================================================                                                                                      |
      | Outputs & filters:                                                                                                                                          |
      | -------------------------------------                                                                                                                       |
      |   0 - output([test_tbl1.id]), filter(nil), rowset=16                                                                                                        |
      |       sort_keys([MATCH(test_tbl1.detail) AGAINST('oceanbase simple text retreival scan on fulltext index'), DESC])                                          |
      |   1 - output([test_tbl1.id], [MATCH(test_tbl1.detail) AGAINST('oceanbase simple text retreival scan on fulltext index')]), filter([MATCH(test_tbl1.detail)  |
      |       AGAINST('oceanbase simple text retreival scan on fulltext index')]), rowset=16                                                                        |
      |       access([test_tbl1.__pk_increment], [test_tbl1.id]), partitions(p0)                                                                                    |
      |       is_index_back=false, is_global_index=false, filter_before_indexback[false],                                                                           |
      |       range_key([test_tbl1.id], [test_tbl1.__pk_increment]), range(3,MIN ; 3,MAX),                                                                          |
      |       range_cond([test_tbl1.id = 3]), has_functional_lookup=true                                                                                            |
      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      16 rows in set
      
    3. The MATCH AGAINST expression does not contain filtering semantics, cannot filter the result set, and cannot scan the full-text index. Therefore, the main table is scanned.

      EXPLAIN SELECT id, digest, detail
              FROM test_tbl1
              WHERE MATCH (detail) AGAINST ('oceanbase')
                  OR id = 3;
      

      The returned result is as follows:

      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      | Query Plan                                                                                                                                                  |
      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      | ====================================================                                                                                                        |
      | |ID|OPERATOR       |NAME     |EST.ROWS|EST.TIME(us)|                                                                                                        |
      | ----------------------------------------------------                                                                                                        |
      | |0 |TABLE FULL SCAN|test_tbl1|5       |503         |                                                                                                        |
      | ====================================================                                                                                                        |
      | Outputs & filters:                                                                                                                                          |
      | -------------------------------------                                                                                                                       |
      |   0 - output([test_tbl1.id], [test_tbl1.digest], [test_tbl1.detail]), filter([MATCH(test_tbl1.detail) AGAINST('oceanbase') OR test_tbl1.id = 3]), rowset=16 |
      |       access([test_tbl1.__pk_increment], [test_tbl1.detail], [test_tbl1.id], [test_tbl1.digest]), partitions(p0)                                            |
      |       is_index_back=false, is_global_index=false, filter_before_indexback[false],                                                                           |
      |       range_key([test_tbl1.__pk_increment]), range(MIN ; MAX)always true, has_functional_lookup=true                                                        |
      +-------------------------------------------------------------------------------------------------------------------------------------------------------------+
      11 rows in set
      
    4. The MATCH AGAINST expression does not contain filtering semantics, cannot filter the result set, and cannot scan the full-text index. However, the idx_test_tbl1 index is hit. Therefore, the idx_test_tbl1 index is scanned.

      EXPLAIN SELECT id
              FROM test_tbl1
              WHERE MATCH (detail) AGAINST ('oceanbase')
                  OR id = 3;
      

      The returned result is as follows:

      +------------------------------------------------------------------------------------------------------------------------------+
      | Query Plan                                                                                                                   |
      +------------------------------------------------------------------------------------------------------------------------------+
      | ===================================================================                                                          |
      | |ID|OPERATOR       |NAME                    |EST.ROWS|EST.TIME(us)|                                                          |
      | -------------------------------------------------------------------                                                          |
      | |0 |TABLE FULL SCAN|test_tbl1(idx_test_tbl1)|5       |503         |                                                          |
      | ===================================================================                                                          |
      | Outputs & filters:                                                                                                           |
      | -------------------------------------                                                                                        |
      |   0 - output([test_tbl1.id]), filter([MATCH(test_tbl1.detail) AGAINST('oceanbase') OR test_tbl1.id = 3]), rowset=16          |
      |       access([test_tbl1.__pk_increment], [test_tbl1.id]), partitions(p0)                                                     |
      |       is_index_back=false, is_global_index=false, filter_before_indexback[false],                                            |
      |       range_key([test_tbl1.id], [test_tbl1.__pk_increment]), range(MIN,MIN ; MAX,MAX)always true, has_functional_lookup=true |
      +------------------------------------------------------------------------------------------------------------------------------+
      11 rows in set
      
    5. The MATCH AGAINST expression contains filtering semantics and scans the corresponding full-text index ft_idx1_test_tbl1. Additionally, the LIMIT clause is pushed down to the full-text index scan as top-k.

      EXPLAIN SELECT id, digest, detail
              FROM test_tbl1
              WHERE MATCH (detail) AGAINST ('oceanbase')
                  LIMIT 3;
      

      The returned result is as follows:

      +------------------------------------------------------------------------------------------------------------------+
      | Query Plan                                                                                                       |
      +------------------------------------------------------------------------------------------------------------------+
      | ===========================================================================                                      |
      | |ID|OPERATOR           |NAME                        |EST.ROWS|EST.TIME(us)|                                      |
      | ---------------------------------------------------------------------------                                      |
      | |0 |TEXT RETRIEVAL SCAN|test_tbl1(ft_idx1_test_tbl1)|4       |31          |                                      |
      | ===========================================================================                                      |
      | Outputs & filters:                                                                                               |
      | -------------------------------------                                                                            |
      |   0 - output([test_tbl1.id], [test_tbl1.digest], [test_tbl1.detail]), filter(nil), rowset=16                     |
      |       access([test_tbl1.__pk_increment], [test_tbl1.detail], [test_tbl1.id], [test_tbl1.digest]), partitions(p0) |
      |       is_index_back=true, is_global_index=false,                                                                 |
      |       calc_relevance=true, match_expr(MATCH(test_tbl1.detail) AGAINST('oceanbase')),                             |
      |       pushdown_match_filter(MATCH(test_tbl1.detail) AGAINST('oceanbase')),                                       |
      |       sort_keys([MATCH(test_tbl1.detail) AGAINST('oceanbase'), DESC]), limit(3), offset(nil), with_ties(false)   |
      +------------------------------------------------------------------------------------------------------------------+
      13 rows in set
      

    References

    Full-text query

    Previous topic

    IS_UUID
    Last

    Next topic

    NVL
    Next
    What is on this page
    Purpose
    Syntax
    Parameters
    mode_flag
    Considerations
    Execution method of text retrieval
    Examples
    Example of text retrieval execution plan
    References