ISO/IEC 9075-3:2023/Cor 1:2026

• Status: Published
• Publication Date: 02-Aug-2026
• ICS: 35.060 - Languages used in information technology
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 3 - Database language
• Current Stage: 6060 - International Standard published
• Start Date: 03-Aug-2026
• Completion Date: 03-Aug-2026

• Corrects: ISO/IEC 9075-3:2023 - Information technology — Database languages SQL — Part 3: Call-Level Interface (SQL/CLI)
• Effective Date: 07-Jan-2026

Overview

ISO/IEC 9075-3:2023/Cor 1:2026 is a technical corrigendum to the international standard for SQL, specifically addressing the Call-Level Interface (SQL/CLI) as defined in ISO/IEC 9075-3:2023. Developed by ISO/IEC Joint Technical Committee 1 (JTC 1), Subcommittee SC 32 (Data Management and Interchange), this corrigendum provides essential clarifications, corrections, and refinements to enhance the accuracy and consistency of implementing SQL Call-Level Interface specifications.

The SQL/CLI standard enables database applications to interact efficiently with SQL databases through procedural APIs, facilitating tasks such as statement preparation, execution, and result processing. This corrigendum addresses technical issues and corrects ambiguities, supporting worldwide interoperability and reliability in information technology systems.

Key Topics

• Call-Level Interface (SQL/CLI) Enhancements
  Refines interface specifications for preparing and executing SQL statements using call-level routines in applications.

• Statement Preparation and Execution
  Clarifies parameter definitions, signature conventions, and the handling of prepared statements, ensuring implementations align with the revised rules.

• Exception Condition Codes
  Updates error-handling mechanisms by correcting exception codes (e.g., condition HY016), fostering consistent error reporting across different implementations.

• Descriptor Management
  Provides corrected instructions for handling row descriptors in routines such as CopyDesc() and SetDescRec(), ensuring the integrity of descriptor operations.

• SQLSTATE Codes
  Revises specific SQLSTATE codes used for signaling exceptions, promoting standardized status reporting in SQL/CLI environments.

Applications

The technical corrections in ISO/IEC 9075-3:2023/Cor 1:2026 deliver practical value for a diverse range of stakeholders in the database technology ecosystem:

• Database Vendors & Developers
  Supports accurate implementation and maintenance of ODBC, JDBC, and other SQL/CLI-based APIs, enhancing compatibility and reducing software defects.

• Enterprise IT Teams
  Helps ensure database middleware operates according to updated standards, improving the reliability and predictability of mission-critical systems.

• Software Testers and Quality Assurance
  Provides a verified baseline to test and validate SQL/CLI products, facilitating compliance and reducing interoperability issues.

• Academic and Research Institutions
  Assists in curriculum development and research by supplying the most up-to-date and precise understanding of SQL/CLI interactions and error management.

By incorporating the corrections from this corrigendum, organizations minimize the risk of inconsistent exception handling and undefined interface behavior, which is vital for robust, portable, and standards-compliant database applications.

Related Standards

When implementing or referencing ISO/IEC 9075-3:2023/Cor 1:2026, consider its relation to the following related standards:

• ISO/IEC 9075-1: Information technology - Database languages - SQL - Part 1: Framework
• ISO/IEC 9075-2: Information technology - Database languages - SQL - Part 2: Foundation (SQL/Foundation)
• ISO/IEC 9075-4: Information technology - Database languages - SQL - Part 4: Persistent Stored Modules (SQL/PSM)
• ISO/IEC 9075-11: Information technology - Database languages - SQL - Part 11: Information and Definition Schemas (SQL/Schemata)

These standards collectively define the structure, syntax, and protocol for SQL and its interfaces, ensuring full interoperability and functionality within database systems.

---

Keywords: ISO/IEC 9075-3:2023/Cor 1:2026, SQL/CLI, Call-Level Interface, database standard, technical corrigendum, SQLSTATE, exception code HY016, descriptor management, database interoperability, information technology, database languages, SQL standards.

International
Standard
ISO/IEC 9075-3
Sixth edition
Information technology — Database
2023-06
languages SQL —
TECHNICAL
Part 3:
CORRIGENDUM 1
Call-Level Interface (SQL/CLI)
2026-08
TECHNICAL CORRIGENDUM 1
Technologies de l’information — Langage de base de données
SQL —
Partie 3: Interface de niveau d’appel (SQL/CLI)
RECTIFICATIF TECHNIQUE 1
Reference number
ISO/IEC 9075-3:2023/Cor. 1:2026(en) © ISO/IEC 2026

ISO/IEC 9075-3:2023/Cor. 1:2026(en)
© ISO/IEC 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC 9075-3:2023/Cor.1:2026(en)
Technical Corrigendum 1 to ISO/IEC 9075-3:2023 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 32, Data management and interchange.
© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC 9075-3:2023/Cor. 1:2026(en)
6 Call-LevelInterfacespecifications
6.4 Preparingastatement
1. Rationale: TodefineanundefinedsymbolforthecallingSubroutines.
ReplacetheSubclauseSignatureandGeneralRule1)with:
SubclauseSignature
“Preparing a statement” [GeneralRules] (
Parameter: “ALLOCATED STATEMENT”,
Parameter: “TEXT LENGTH”,
Parameter: “STATEMENT TEXT”,
Parameter: “INVOKER”
) Returns: “PREP”
ALLOCATEDSTATEMENT—anallocatedSQL-statementdescriptor.
TEXTLENGTH—thelengthofSTATEMENTTEXT,ortheNULLTERMINATEDindication(-3).
STATEMENTTEXT—thetextofanSQL-statementtobepreparedforexecution.
INVOKER—acharacterstringidentifyingtheSubclausethatinvokedthisSubclause(e.g.,
'ExecDirect','Prepare',or'ParamData').
PREP—thepreparedstatement.
GeneralRules
1) LetSbetheALLOCATEDSTATEMENT,letTLbetheTEXTLENGTH,letSTbetheSTATEMENT
TEXT,andletINVbetheINVOKERinanapplicationoftheGeneralRulesofthisSubclause.The
resultoftheapplicati
...