v3.0

About MogDB
- MogDB Introduction
- Comparison Between MogDB and openGauss
- MogDB Release Notes
- Open Source Components
- Usage Limitations
- Terms of Use
Quick Start
- MogDB Playground
- Container-based MogDB Installation
- Installation on a Single Node
- MogDB Access
  - Use CLI to Access MogDB
    - gsql
    - pgcli
  - Use GUI to Access MogDB
  - Use Middleware to Access MogDB
    - Use WebLogic to Configure MogDB Data Sources
    - Use WebSphere to Configure MogDB Data Sources
  - Use Programming Language to Access MogDB
    - Java
    - C/C++
    - Python
    - Go
    - Rust
    - NodeJS
    - .Net
- Using Sample Dataset Mogila
Characteristic Description
Installation Guide
- Installation Preparation
  - Environment Requirement
  - Operating System Configuration
- Container Installation
- PTK-based Installation
- OM-based Installation
- Manual Installation
- Recommended Parameter Settings
Administrator Guide
AI Features Guide
- AI Features Overview
- AI4DB: Autonomous Database O&M
  - DBMind Mode
  - Components that Support DBMind
    - Prometheus Exporter
  - AI Sub-functions of the DBMind
    - X-Tuner: Parameter Tuning and Diagnosis
    - Index-advisor: Index Recommendation
    - AI4DB: Root Cause Analysis for Slow SQL Statements
    - AI4DB: Trend Prediction
    - SQLdiag: Slow SQL Discovery
- DB4AI: Database-driven AI
  - Native DB4AI Engine
  - Full-process AI
    - PLPython Fenced Mode
    - DB4AI-Snapshots for Data Version Management
- AI in DB
  - Intelligence Explain: SQL Statement Query Time Prediction
Security Guide
- Database Security Management
Developer Guide
- Application Development Guide
  - Development Specifications
  - Development Based on JDBC
  - Development Based on ODBC
  - Development Based on libpq
    - Dependent Header Files of libpq
    - Development Process
    - Example
    - Link Parameters
    - libpq API Reference
      - Database Connection Control Functions
        Description
        PQconnectdbParams
        PQconnectdb
        PQconninfoParse
        PQconnectStart
        PQerrorMessage
        PQsetdbLogin
        PQfinish
        PQreset
        PQstatus
      - Database Statement Execution Functions
        PQclear
        PQexec
        PQexecParams
        PQexecParamsBatch
        PQexecPrepared
        PQexecPreparedBatch
        PQfname
        PQgetvalue
        PQnfields
        PQntuples
        PQprepare
        PQresultStatus
      - Functions for Asynchronous Command Processing
        Description
        PQsendQuery
        PQsendQueryParams
        PQsendPrepare
        PQsendQueryPrepared
        PQflush
      - Functions for Canceling Queries in Progress
        PQgetCancel
        PQfreeCancel
        PQcancel
  - Psycopg-Based Development
  - Commissioning
- Stored Procedure
- User Defined Functions
- PL/pgSQL-SQL Procedural Language
  - Overview of PL/pgSQL Functions
  - Data Types
  - Data Type Conversion
  - Arrays and Records
  - DECLARE Syntax
  - Basic Statements
  - Dynamic Statements
  - Control Statements
  - Transaction Management
  - Other Statements
  - Cursors
  - Advanced Packages
    - Basic Interfaces
      - PKG_SERVICE
  - Retry Management
  - Debugging
  - package
- Scheduled Jobs
  - PKG_SERVICE API
- Autonomous Transaction
- Logical Replication
  - Logical Decoding
    - Overview
    - Logical Decoding by SQL Function Interfaces
  - Publication-Subscription
- Foreign Data Wrapper
- Materialized View
  - Materialized View Overview
  - Full Materialized View
  - Incremental Materialized View
- Partition Management
  - Partition Pruning
  - Recommendations For Choosing A Partitioning Strategy
Performance Tuning Guide
Reference Guide
Common Faults and Identification
- Common Fault Locating Methods
- Common Fault Locating Cases
  - Core Fault Locating
  - Permission/Session/Data Type Fault Location
  - Service/High Availability/Concurrency Fault Location
  - Table/Partition Table Fault Location
    - Table Size Does not Change After VACUUM FULL Is Executed on the Table
    - An Error Is Reported When the Table Partition Is Modified
  - File System/Disk/Memory Fault Location
  - SQL Fault Location
  - Index Fault Location
Source Code Parsing
FAQs
Glossary
Mogeaver
- Overview
- Release Notes

SQLFetch

Function

SQLFetch is used to advance the cursor to the next row of the result set and retrieve any bound columns.

Prototype

CSQLRETURN SQLFetch(SQLHSTMT    StatementHandle);

Parameter

Table 1 SQLFetch parameters

Keyword	Parameter Description
StatementHandle	Statement handle, obtained from SQLAllocHandle.

Return Value

SQL_SUCCESS indicates that the call succeeded.
SQL_SUCCESS_WITH_INFO indicates that some warning information is displayed.
SQL_ERROR indicates major errors, such as memory allocation and connection failures.
SQL_NO_DATA indicates that the SQL statement does not return a result set.
SQL_INVALID_HANDLE indicates that invalid handles were called. This value may also be returned by other APIs.
SQL_STILL_EXECUTING indicates that the statement is being executed.

Precautions

If SQLFetch returns SQL_ERROR or SQL_SUCCESS_WITH_INFO, the application can call SQLGetDiagRec, with HandleType and Handle set to SQL_HANDLE_STMT and StatementHandle, respectively, to obtain the SQLSTATE value. The SQLSTATE value provides the detailed function calling information.

Example