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

ISO/IEC 9075-3:2023/Cor 1:2026 is an ISO technical corrigendum to Part 3 of SQL, the Call-Level Interface (SQL/CLI). It corrects specific call-level interface routines and status-code text in the base 2023 edition, so it is mainly for database engine implementers, client-library developers, and conformance test teams that validate SQL/CLI behavior.

What does ISO/IEC 9075-3:2023/Cor 1:2026 specify?

ISO/IEC 9075-3:2023/Cor 1:2026 specifies corrections to the SQL/CLI text in Clause 6, Clause 7, and Clause 10 of ISO/IEC 9075-3. It updates the wording and references used by statement-preparation routines, descriptor-copying routines, and the SQLSTATE mapping for one exception condition.

The document is organized as a set of targeted replacement instructions with rationale notes, followed by the corrected text to insert in the affected subclauses and table entry.

Part of the document	What it covers
Clause 6.4	Revised “Preparing a statement” subclause signature and general rules
Clause 7.14, 7.58	Exception handling for CopyDesc() and SetDescRec()
Clause 7.20, 7.51	Use of the revised preparation logic in ExecDirect() and Prepare()
Clause 10.1, Table 46	SQLSTATE class and subclass code for one CLI-specific condition

What are the key requirements of ISO/IEC 9075-3:2023/Cor 1:2026?

The corrigendum changes how SQL/CLI describes statement preparation and how two descriptor routines report an error. In practice, implementers need to align routine signatures, internal references, and SQLSTATE reporting with the corrected text.

• Clause 6.4, “Preparing a statement” now uses a revised subclause signature with the parameters ALLOCATED STATEMENT, TEXT LENGTH, STATEMENT TEXT, and INVOKER, and it returns PREP. This matters because client code and the implementation need a single, explicit preparation interface.
• The general rules for Clause 6.4 state how those parameters are bound and how the result is returned as PREP. That gives a consistent preparation flow for routines that call into the subclause.
• Clause 6.4 also ties the implicit DESCRIBE USING behavior to the allocated statement descriptor. In practice, the statement being prepared is the object that is described and passed onward.
• ExecDirect() and Prepare() are updated to call the corrected Clause 6.4 rules with their own INVOKER values. This means both routines share the same preparation logic while still identifying which routine invoked it.
• CopyDesc() and SetDescRec() now raise the same CLI-specific condition when the target is an implementation row descriptor. Implementers need to block modification of that descriptor type and return the corrected error.
• Clause 10.1 updates the SQLSTATE table entry for the condition cannotmodifyanimplementationrowdescriptor. That keeps application-visible error reporting aligned with the corrected exception handling.

What terms does ISO/IEC 9075-3:2023/Cor 1:2026 define?

• SQL/CLI - The SQL Call-Level Interface, used by applications and libraries to execute SQL statements through a programming interface.
• ALLOCATED STATEMENT - An allocated SQL-statement descriptor passed into the preparation rules.
• TEXT LENGTH - The length of STATEMENT TEXT, or the NULL TERMINATED indication.
• STATEMENT TEXT - The SQL statement text that is being prepared for execution.
• INVOKER - A character string naming the subclause that called the preparation logic, such as ExecDirect, Prepare, or ParamData.
• PREP - The prepared statement returned by the preparation rules.
• implementation row descriptor - A descriptor type that cannot be modified in the corrected CopyDesc() and SetDescRec() rules.
• SQLSTATE - The SQL status-code system used to report classes and subclass conditions, including CLI-specific errors.

Who uses ISO/IEC 9075-3:2023/Cor 1:2026?

ISO/IEC 9075-3:2023/Cor 1:2026 is used by people who build, test, or validate SQL client interfaces. That includes DBMS vendors, driver and middleware developers, QA teams, standards conformance labs, and technical buyers who need to confirm that a product follows the current SQL/CLI text.

It is especially relevant where code calls Prepare(), ExecDirect(), CopyDesc(), or SetDescRec(), or where error handling depends on the SQLSTATE value for the implementation row descriptor condition.

What changed in ISO/IEC 9075-3:2023/Cor 1:2026 from the previous edition?

ISO/IEC 9075-3:2023/Cor 1:2026 is Technical Corrigendum 1 to ISO/IEC 9075-3:2023. It makes these corrections:

• Replaces the subclause signature and general rules in Clause 6.4.
• Deletes two general rules in Clause 6.4.
• Corrects the invocation references in Clause 7.20 ExecDirect() and Clause 7.51 Prepare().
• Corrects the exception condition in Clause 7.14 CopyDesc() and Clause 7.58 SetDescRec().
• Corrects the SQLSTATE row for cannotmodifyanimplementationrowdescriptor in Table 46.

Which standards are used with ISO/IEC 9075-3:2023/Cor 1:2026?

• ISO/IEC 9075-3:2023 - The base edition of Part 3, Call-Level Interface (SQL/CLI), that this corrigendum amends.

What does the ISO/IEC 9075-3:2023/Cor 1:2026 document contain?

The document contains front matter, a set of correction instructions with short rationales, and the replacement text for the affected SQL/CLI passages. It revises one statement-preparation subclause, two descriptor routines, two routine calls that rely on the revised preparation rules, and one SQLSTATE table entry.

For implementers and test teams, the practical value is in the exact replacement text and the corrected error mapping. For standards maintenance work, it shows precisely which clause fragments and table entry need to be updated in the base edition.

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