ISO/IEC 9075-13: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-13:2023 - Information technology — Database languages SQL — Part 13: SQL Routines and types using the Java TM programming language (SQL/JRT)
• Effective Date: 07-Jan-2026

ISO/IEC 9075-13:2023/Cor 1:2026 is ISO Technical Corrigendum 1 to Part 13 of the SQL standard, which covers SQL routines and types using the Java TM programming language (SQL/JRT). It corrects and clarifies conformance text in the clauses on concepts, routine invocation, schema definition, and Java topics. Use it when you need the amended wording for SQL/JRT implementations, conformance checks, or test documentation.

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

ISO/IEC 9075-13:2023/Cor 1:2026 amends ISO/IEC 9075-13:2023 rather than adding a new subject area. Its changes are concentrated in clause 4, clause 9, clause 10, and clause 13, where the corrigendum replaces specific paragraphs and conformance rules.

Clause	Topic
4.12.2	JARs - Deployment descriptor files
9.4	<routineinvocation>
10.1	<dropschemastatement>
10.4	<user-definedtypedefinition>
13.2	Java topics - Deployment descriptor files

The practical focus is feature-based conformance. The corrected text ties behavior to Feature J531, "Deployment", Feature J511, "Commands", Feature J611, "References", and Feature J591, "Overloading".

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

Deployment descriptor files

• Clause 4.12.2 clarifies that the document provides a way to execute SQL schema statement variants by requesting deployment during invocation of SQLJ.INSTALL_JAR and SQLJ.REMOVE_JAR. In practice, an implementation has to follow the chosen deployment path consistently when it supports this mechanism.
• Clause 4.12.2 also states that a conforming SQL implementation is required to support either deployment descriptor based execution of SQL schema statements through Feature J531, "Deployment", or embedded SQL through Feature J511, "Commands". The corrigendum makes clear that both mechanisms do not have to be supported at the same time.

Routine invocation rules

• Clause 9.4 replaces the conformance rules for <routineinvocation> so that, without Feature J611, "References", a conforming SQL language shall not contain a <SQL-invokedroutine> with a <languagename> containing JAVA and a <referencevalueexpression>. This matters when checking which Java-related routine calls are permitted in SQL text.
• Clause 9.4 also restricts a JAVA routine invocation that contains a <rightarrow> when Feature J611 is absent. That gives implementers and testers a precise feature gate for Java reference syntax.

Schema definition and manipulation

• Clause 10.1 updates the lead test of General Rule 12 for <dropschemastatement> so that it applies when the SQL implementation supports Feature J511, "Commands". In practice, this aligns the drop-schema rule with the optional command-support feature.
• Clause 10.4 replaces the conformance rule for <user-definedtypedefinition>. Without Feature J591, "Overloading", a conforming SQL language shall not contain a <user-definedtypebody> with an <externalJavatypeclause> and a <methodspecification> whose <methodname> is equivalent to another method name in the same user-defined type definition. This prevents duplicate equivalent method names unless overloading is supported.

Java topics and descriptor-file restrictions

• Clause 13.2 replaces the conformance rules for <descriptor file> content when Feature J531, "Deployment", is absent. The corrigendum lists the SQL statements that must not appear there, including user-defined type definition, drop data type, SQL-invoked routine, drop routine, user-defined ordering definition, drop user-defined ordering, grant privilege, and revoke. In practice, this is the main check for what a deployment descriptor may contain in a non-deployment implementation.

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

• SQL/JRT - The part of SQL that covers routines and types using the Java TM programming language.
• Technical Corrigendum 1 - A correction document that updates specific wording in ISO/IEC 9075-13:2023.
• deployment descriptor file - A file used to request deployment-based execution of SQL schema statements.
• descriptor file - The file type governed by the conformance rules in clause 13.2.
• SQL-invoked routine - A routine that is invoked from SQL text.
• Feature J531, "Deployment" - The optional capability for deployment descriptor based execution of SQL schema statements.
• Feature J611, "References" - The optional capability that affects Java routine invocations using reference expressions and arrows.
• Feature J591, "Overloading" - The optional capability that allows method-name overloading in user-defined type definitions.

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

• Database engine vendors implementing SQL/JRT support.
• Conformance and quality teams checking feature-dependent SQL behavior.
• Tool vendors generating deployment descriptor files or Java-related SQL definitions.
• Architects and integrators who need to know which Java-linked SQL constructs are permitted under specific optional features.
• Buyers and technical reviewers comparing SQL implementation support against the amended conformance rules.

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

ISO/IEC 9075-13:2023/Cor 1:2026 is Technical Corrigendum 1 to ISO/IEC 9075-13:2023. The corrigendum states these changes:

• Clause 4.12.2 is clarified so that deployment descriptor based execution is described together with SQLJ.INSTALL_JAR and SQLJ.REMOVE_JAR.
• Clause 9.4 replaces the <routineinvocation> conformance rules to avoid over-restriction without Feature J611, "References".
• Clause 10.1 updates the lead test of General Rule 12 for <dropschemastatement> when Feature J511, "Commands", is supported.
• Clause 10.4 replaces the conformance rule for <user-definedtypedefinition> when Feature J591, "Overloading", is absent.
• Clause 13.2 replaces the conformance rules for descriptor-file content when Feature J531, "Deployment", is absent.

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

The document contains targeted replacement text, not a full rewrite of Part 13. It gives rationale notes and updated conformance rules for deployment descriptors, routine invocation, drop schema behavior, user-defined type definitions, and Java topics.

It is organized as short corrections to existing clauses, so implementers can update parsing, validation, and test cases without re-reading the whole SQL/JRT part. The most practical content is the feature-based restriction language tied to J531, J511, J611, and J591.

For testing and certification work, the corrigendum is useful because it identifies exactly which SQL statements and Java-related constructs are allowed or disallowed under each optional feature.

International
Standard
ISO/IEC 9075-13
Fifth edition
Information technology — Database
2023-06
languages SQL —
TECHNICAL
Part 13:
CORRIGENDUM 1
SQL Routines and types using the
2026-08
Java TM programming language
(SQL/JRT)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données
SQL —
Partie 13: Routines et types de SQL utilisant le langage de
programmation Java TM (SQL/JRT)
RECTIFICATIF TECHNIQUE 1
Reference number
ISO/IEC 9075-13:2023/Cor. 1:2026(en) © ISO/IEC 2026

ISO/IEC 9075-13: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-13:2023/Cor.1:2026(en)
Technical Corrigendum 1 to ISO/IEC 9075-13: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-13:2023/Cor. 1:2026(en)
4 Concepts
4.12 JARs
4.12.2 Deploymentdescriptorfiles
1. Rationale: Clarifythetext.
Replacethe3rdparagraphwith:
ThisdocumentprovidesamechanismtoexecuteitsvariantsofSQL-schemastatements,namelyby
requestingdeploymentduringinvocationofSQLJ.INSTALL_JARandSQLJ.REMOVE_JARprocedures.
AconformingSQL-implementationisrequiredtosupportdeploymentdescriptorbasedexecution
ofitsSQL-schemastatements(FeatureJ531,“Deployment”)orembeddedSQL(FeatureJ511,“Com-
mands”);aconformingSQL-implementationisnotrequiredtosupportbothmechanisms.
9 Additionalcommonelements
9.4
1. Rationale: PreventConformanceRulesfrombeingover-restrictive.
ReplacetheConformanceRules1)and2)with:
1) InsertafterthelastCR: WithoutFeatureJ611,“References”,conformingSQLlanguageshall
notcontainanthatcontainsathatcontainsJAVA
andthatcontainsa.
2) Insertafte
...