ISO/IEC 9075-2: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-2:2023 - Information technology — Database languages SQL — Part 2: Foundation (SQL/Foundation)
• Effective Date: 07-Jan-2026

ISO/IEC 9075-2:2023/Cor 1:2026 is ISO’s Technical Corrigendum 1 to ISO/IEC 9075-2:2023, the Foundation part of the SQL database language standard. It corrects SQL/Foundation rules for expressions, query processing, predicates, JSON handling, routines, embedded SQL, and conformance. The document is for implementers, testers, and buyers who need the published SQL/Foundation text to reflect these corrections.

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

ISO/IEC 9075-2:2023/Cor 1:2026 specifies clause-by-clause corrections to SQL/Foundation. It amends syntax rules, general rules, and conformance rules in the Foundation part of SQL, and it also updates two informative annexes.

The corrigendum is organized as direct replacements, insertions, and deletions against the published part 2 text. The affected areas are Clauses 4 to 13, Clause 21, Clause 25, Annex F, and Annex H.

Annex	What it covers
Annex F	Incompatibilities with ISO/IEC 9075:2016
Annex H	SQL mandatory feature taxonomy

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

The corrigendum mainly tightens SQL semantics where implementations need to behave consistently. For readers, that means parser, optimizer, executor, and conformance-test rules may need updating in several specific areas.

Nullability inference and grouped query logic

Clause 4 and Clause 7 refine how SQL infers nullability when Feature T101, “Enhanced nullability determination”, is supported. The text now ties certain deductions to implementation-defined rules and clarifies when a boolean value expression can be treated as a known-not-null condition.

In practice, this matters for query optimization and validation. An implementation can use the corrected wording to infer when values cannot be null, which affects rewrite rules, join logic, and expression evaluation.

Clause 4 also revises the definition of a grouped table and the behavior of GROUPING(<value expression>). The grouped-table text now states how rows are partitioned into groups, and GROUPING() is defined in terms of grouping sets, CUBE, ROLLUP, and UNION branches.

In practice, this tells implementers exactly how to assign rows to groups and when GROUPING() returns 1 or 0. That affects grouped query results and any tooling that checks grouping semantics.

Character handling and truncation

Clause 5 and Clause 9 correct the definition of <truncating whitespace> and its use in store assignment. <truncating whitespace> is an implementation-defined subset of whitespace characters that must include space, and it is used when fixed-length or variable-length character values are shortened.

In practice, this changes how trailing characters are tested before right truncation is accepted. If the extra characters are all truncating whitespace, assignment can succeed; otherwise, the standard raises a string-data right-truncation exception.

Expression and function behavior

Clause 6 corrects several scalar-expression rules. It updates <windowfunction>, <caseexpression>, <nextvalueexpression>, <numericvaluefunction>, <stringvaluefunction>, and <JSONsimplifiedaccessor> so the symbols and evaluation rules are aligned.

In practice, implementers get clearer behavior for lead/lag defaults, row pattern measures, sequence generation in queries and updates, trigonometric and logarithmic error handling, and the equivalent forms of JSON accessors. These corrections matter because they define what value is produced, or which exception is raised, when a function is evaluated.

Clause 10 also corrects <aggregatefunction> and <JSONaggregatefunction>. The corrigendum updates the error conditions for inverse distribution functions and the handling of JSON aggregate values.

In practice, this affects aggregate computation and the way applications see function failures, especially when a function argument is outside the allowed range.

Query expressions, joins, and predicates

Clauses 7 and 8 extend or tighten several query and predicate rules. The corrigendum adds table types that support lateral join, refines nullability treatment in joined tables and query specifications, and corrects the HAVING rule.

It also adds or adjusts conformance restrictions for several predicates, including <likepredicate>, <similarpredicate>, <regexlikepredicate>, <normalizedpredicate>, <matchpredicate>, <overlapspredicate>, <distinctpredicate>, <memberpredicate>, <submultisetpredicate>, <setpredicate>, <typepredicate>, and <JSONpredicate>.

In practice, this tells an implementation when a predicate form is permitted and which feature code must be present. That is important for feature claims, SQL dialect support, and parser acceptance.

Polymorphic table functions and SQL-invoked routines

Clauses 9 and 11 correct the rules for polymorphic table function (PTF) processing, including the signatures of PTF component procedures and the ONLY PASSTHROUGH return mode. The corrigendum also adjusts how SQL-invoked routines relate to those signatures.

In practice, this is the interface contract for PTF components such as describe, start, fulfill, and finish procedures. Implementers need these corrected signatures so that routine parameter lists match the required component behavior.

Module language, embedded SQL, and conformance

Clauses 13 and 21 adjust module-language and embedded-SQL conformance rules. The corrigendum corrects which host-language and routine-language features are linked to Feature E182, “Modulelanguage”, and it tightens the use of CLOB-related variables in embedded C and COBOL programs.

In practice, this affects claims of support for module language and embedded SQL in Ada, C, COBOL, Fortran, MUMPS, Pascal, and PL/I environments. It also tells conformance test authors what must be present or absent in a conforming SQL language implementation.

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

• SQL/Foundation - The Foundation part of SQL that defines the core database-language behavior corrected by this document.
• grouped table - A table formed from groups created during evaluation of a <groupbyclause>, with each row belonging to exactly one group.
• GROUPING() - A grouping operation that returns 1 or 0 depending on whether a value expression is omitted in the generated grouping branch.
• <truncating whitespace> - An implementation-defined subset of whitespace characters used when right-truncation of character data is checked.
• PTF - A polymorphic table function, with describe, start, fulfill, and finish component procedures governed by corrected signature rules.
• Feature T101, “Enhanced nullability determination” - The feature that allows an SQL implementation to infer when an expression or column cannot be null.
• ONLY PASSTHROUGH - A PTF return mode that changes how component procedure signatures are built and checked.

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

ISO/IEC 9075-2:2023/Cor 1:2026 is used by SQL database engine developers, query optimizer teams, parser and compiler engineers, and test authors who need the corrected Foundation rules. It is also relevant to quality managers and certification teams checking conformance claims against specific SQL features.

Organizations that integrate SQL with host languages such as Ada, C, COBOL, Fortran, MUMPS, Pascal, and PL/I use it for module language and embedded SQL behavior. Buyers and architects use it to judge whether a product’s SQL/Foundation claim includes the features and corrections they need.

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

ISO/IEC 9075-2:2023/Cor 1:2026 is a technical corrigendum to ISO/IEC 9075-2:2023. The corrections stated in the document include:

• clearer nullability inference wording for Feature T101
• a revised definition of grouped tables
• a clarified definition of GROUPING()
• corrected <truncating whitespace> handling in store assignment
• updates to window functions, NEXT VALUE, numeric functions, string functions, and JSON simplified accessors
• corrections to PTF component signatures and SQL-invoked routine rules
• updated conformance rules for module language and embedded SQL
• revised informative notes in Annex F and Annex H

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

The document contains textual corrections rather than a new standalone SQL feature set. It provides replacement paragraphs, revised syntax rules, updated general rules, and conformance-rule edits across multiple clauses of SQL/Foundation.

It also updates Table 42 on implied feature relationships and Table H.1 on the mandatory feature taxonomy. Annex F adds an incompatibility item describing changed exception conditions, while Annex H removes and revises feature-taxonomy entries tied to module language support.

For implementers, the most useful content is the exact rule text that corrects parsing, evaluation, error conditions, and feature-claim behavior. For testers, it identifies the areas where a SQL/Foundation implementation should be checked for alignment with the corrected semantics.

International
Standard
ISO/IEC 9075-2
Sixth edition
Information technology — Database
2023-06
languages SQL —
TECHNICAL
Part 2:
CORRIGENDUM 1
Foundation (SQL/Foundation)
2026-08
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données
SQL —
Partie 2: Fondations (SQL/Fondations)
RECTIFICATIF TECHNIQUE 1
Reference number
ISO/IEC 9075-2:2023/Cor. 1:2026(en) © ISO/IEC 2026

ISO/IEC 9075-2: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-2:2023/Cor.1:2026(en)
Technical Corrigendum 1 to ISO/IEC 9075-2: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-2:2023/Cor. 1:2026(en)
4 Concepts
4.15 Columns,fields,andattributes
1. Rationale: Correctlyidentifyimplementation-definedaspectsthataredependentonFeatureT101,
“Enhancednullabilitydetermination”,andremovetheduplicationofthoseaspects.
Replacethe5thbulletofthe4thparagraphwith:
— TheSQL-implementationsupportsFeatureT101,“Enhancednullabilitydetermination”,and
isabletodeducethatthe“CISNULL”canneverbeTruewhen
appliedtoarowinTthroughsomeimplementation-defined(IE011)ruleorrules;
NOTE22—Thenotions“knownnotnullable”and“known-not-nullcondition”areexamplesofsuchadditional
rulesthatanSQL-implementationcanadopt.
4.17 Tables
4.17.14 Groupedtables
1. Rationale: Correctundesiredover-restriction.
Replacethe1stparagraphwith:
Agroupedtableisasetofgroupsderivedduringtheevaluationofa.AgroupGis
acollectionofrowsinwhich,foreverygroupingcolumnGC,ifthevalueofGCinsomerowisGV,then
thevalueofGCineveryrowisnotdistinctfromGV;moreover,ifR1isarowingroupG1ofgrouped
tableGTandR2isarowinGTsuchthatforeverygroupingcolumnGCthevalueofGCinR1isnot
distinctfromthevalueofGCinR2,thenR2isinG1.EveryrowinGTisinexactlyonegroup.Agroup
maybeconsideredasatable.Setfunctionsoperateongroups.
4.18 Dataanalysisoperations
4.18.2 Groupfunctions
1. Rationale: Rewordtoavoidpossibleconfusionofinterpretation.
Replacethe3rdparagraphwith:
ThegroupingoperationisoftheformGROUPING().Theresultofsuchaninvo-
cationis1(one)inthecaseofarowwhosevaluesaretheresultsofaggregationthatomitsthat
fromtheinabranchoftheUNIONALLorUNIONDISTINCT
thatisgeneratedbythesyntactictransformsinSubclause7.13,“”ofagrouped
querycontainingCUBE,ROLLUP,orGROUPINGSETS,and0(zero)otherwise.
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
5 Lexical elements
5.2 and
1. Rationale: The definition of is any consecutive sequence of whitespace characters. This can
beanarbitrarysetsoneedstousethedefinitionofwhitespace,not
.
ReplaceSyntaxRule4)with:
4) isanimplementation-defined(IV074)subsetofcharacterseachof
whichsatisfiesthedefinitionofwhitespacefoundinClause3,“Termsanddefinitions”;the
subsetshallalwaysincludeatleast.
5.4 Namesandidentifiers
1. Rationale: CorrectanincorrectBNFterm.
ReplaceConformanceRule25)with:
25) WithoutFeatureB209,“PTFextendednames”,conformingSQLlanguageshallnotcontaina
ora.
6 Scalarexpressions
6.1
1. Rationale: Referencethecorrecttypedescriptor.
ReplacetheleadtextofGeneralRule20)with:
20) Ifisa,thenacollectiontypedescriptoriscreated.LetKCbethe
kindofcollectionspecifiedby.LetETbetheelementtypeof type>.LetETDbethetypedesignatorofET.Thecollectiontypedescriptorincludesthetype
designatorETDKC,anindicationofKC,thedescriptorofET.
6.10
1. Rationale: Ensurethatsymbolsareproperlydefined.
AddthefollowingSyntaxRules:
2.1) Ifisspecified,then:
a) LetVE1beandletDTbethedeclaredtypeofVE1.
b) Case:
i) Ifisspecified,thenletOFFbe.
ii) Otherwise,letOFFbe1(one).
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
c) Case:
i) Ifisspecified,thenletVE2be.The
declaredtypeofVE2shallbecompatiblewithDT.
ii) Otherwise,letVE2beCAST(NULLASDT).
d) Ifisspecified,thenletNTREATbethe functionnulltreatment>;otherwise,letNTREATbeRESPECTNULLS.
e) ThedeclaredtypeoftheresultisDT.
2.2) LetWNSbethe.LetWDXbeawindowstructuredescriptor
thatdescribesthewindowdefinedbyWNS.
2.3) Athatisashallbeequivalenttothe
containedinaRPMCinthe measures>ofWDX.Thedeclaredtypeoftheisthedeclaredtypeofthe
containedinRPMC.
6.12
1. Rationale: Correctproblemwithsymboldefinition.
InsertthefollowingSyntaxRule:
1) .
b.1) LetNVbethenumberofsdirectlycontainedinthe ation>andfori,1(one)≤i≤NV,letV,bethei-thsuch.
i
2. Rationale: Correctproblemwithsymboldefinition.
ReplaceSyntaxRules2)e),2)f),and2)g)with:
2) .
e) Fori,1(one)≤i≤N:
i) LetWOLbetheofthei-th.
i
ii) LetRbetheofthei-th.
i
iii) LetM(i)bethenumberofssimplycontainedinWOL.
i
iv) Forj,1(one)≤j≤M(i):
1) LetWO bethej-thsimplycontainedinWOL.
i,j i
2) Case:
A) IfWO isa,thenletEWO be
i,j i,j
= WO
i,j
B) Otherwise,letEWO beWO .
i,j i,j
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
6.14
1. Rationale: Addtheapplicationofthevalueofthetotheapproriaterow.
ReplaceGeneralRule1)with:
1) IfNVEisspecified,thenletSEQbethesequencegeneratordescriptor
identifiedbythecontainedinNVE.
Case:
a) IfNVEisdirectlycontainedinaQS,then,foreachrowinthe
resultofQS:
i) GeneralRulesofSubclause9.35,“Generationofthenextvalueofasequence
generator”,areappliedwithSEQasSEQUENCE;letRESbetheRESULTreturned
fromtheapplicationofthoseGeneralRules.
ii) TheresultofeachevaluationofNVEforthatrowisRES.
b) IfNVEisdirectlycontainedinaTVC,then,
foreachcontainedinTVC:
i) GeneralRulesofSubclause9.35,“Generationofthenextvalueofasequence
generator”,areappliedwithSEQasSEQUENCE;letRESbetheRESULTreturned
fromtheapplicationofthoseGeneralRules.
ii) TheresultofeachevaluationofNVEforthat expression>isRES.
c) IfNVEisdirectlycontainedinan,then,foreachrowtobeupdated
bytheor:
i) GeneralRulesofSubclause9.35,“Generationofthenextvalueofasequence
generator”,areappliedwithSEQasSEQUENCE;letRESbetheRESULTreturned
fromtheapplicationofthoseGeneralRules.
ii) TheresultofeachevaluationofNVEforthatrowisRES.
6.31
1. Rationale: Subclause6.31,“”,GeneralRules10)b)i)1)and10)b)ii)1)useda
genericexceptionconditionwhilesimilarrulesuseaspecificexceptioncondition.
ReplaceGeneralRule10)b)with:
10) .
b) Otherwise,letOPbethe.
Case:
i) IfOPisACOS,then
Case:
1) IfVislessthan−1(negativeone)orVisgreaterthan1(one),thenan
exceptionconditionisraised:dataexception—invalidargumentfor
trigonometricfunction(2202M).
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
2) Otherwise,theresultoftheistheinversecosine
ofV.
ii) IfOPisASIN,then
Case:
1) IfVislessthan−1(negativeone)orVisgreaterthan1(one),thenan
exceptionconditionisraised:dataexception—invalidargumentfor
trigonometricfunction(2202M).
2) Otherwise,theresultoftheistheinversesine
ofV.
iii) IfOPisATAN,thentheresultistheinversetangentofV.
iv) IfOPisCOS,thentheresultisthecosineofV.
v) IfOPisCOSH,thentheresultisthehyperboliccosineofV.
vi) IfOPisSIN,thentheresultisthesineofV.
vii) IfOPisSINH,thentheresultisthehyperbolicsineofV.
viii) IfOPisTAN,thentheresultisthetangentofV.
ix) IfOPisTANH,thentheresultisthehyperbolictangentofV.
2. Rationale: Subclause6.31,“”,GeneralRules11)b)and11)c)usedageneric
exceptionconditionwhilesimilarrulesuseaspecificexceptioncondition.
ReplaceGeneralRule11)with:
11) Ifisspecified,thenletVBbethevalueofthe base>andletVAbethevalueofthe.
Case:
a) IfatleastoneofVAandVBisthenullvalue,thentheresultisthenullvalue.
b) IfVAisnegativeor0(zero),thenanexceptionconditionisraised:dataexception—
invalidargumentforgenerallogarithmfunction(2201Z).
c) IfVBisnegative,0(zero),or1(one),thenanexceptionconditionisraised:data
exception—invalidargumentforgenerallogarithmfunction(2201Z).
d) Otherwise,theresultisthelogarithmwithbaseVBofVA.
6.33
1. Rationale: Addmissingalternativeof
ReplaceSyntaxRule1)with:
1) 15Thedeclaredtypeofisthedeclaredtypeoftheimmediatelycontained
,,or.
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
2. Rationale: Addmissingalternativeof
ReplaceGeneralRule1)with:
1) 15Theresultofistheresultoftheimmediatelycontained valuefunction>,,or.
6.36
1. Rationale: Removesuperfluousperiodcausingerrorinsyntactictransformation.
ReplaceSyntaxRule3)a)ii)with:
3) .
a) .
ii) JAisequivalenttothe:
JSON_VALUE ( VEP, 'lax $JC' RETURNING RT
NULL ON EMPTY NULL ON ERROR)
2. Rationale: Removesuperfluousperiodcausingerrorinsyntactictransformation.
ReplaceSyntaxRule3)b)with:
3) .
b) Otherwise,JAisequivalenttothe:
JSON_QUERY ( VEP, 'lax $JC' WITH CONDITIONAL ARRAY WRAPPER
NULL ON EMPTY NULL ON ERROR)
6.46
1. Rationale: Correctlyidentifyimplementation-definedaspectsthataredependentonFeatureT101,
“Enhancednullabilitydetermination”,andremovetheduplicationofthoseaspects.
ReplaceSyntaxRule6)c)with:
6) .
c) IftheSQL-implementationsupportsFeatureT101,“Enhancednullabilitydetermination”,
andifBVEconformstoanimplementation-defined(IE011)rulethatenablestheSQL-
implementationtocorrectlyinferthat,whenBVEisTrue,thenXcannotbenull,then
BVEisaknown-not-nullconditionforX.
7 Queryexpressions
7.6
1. Rationale: Addmissingtabletypetothosethatsupportlateraljoin.
ReplaceSyntaxRule5)with:
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
5) 14 16Athatsimplycontainsanyofthefollowingsupportslateraljoin: derivedtable>,,,,
or.
7.10
1. Rationale: Correctlyidentifyimplementation-definedaspectsthataredependentonFeatureT101,
“Enhancednullabilitydetermination”,andremovetheduplicationofthoseaspects.
ReplaceSyntaxRule14)c)with:
14) .
c) IftheSQL-implementationsupportsFeatureT101,“Enhancednullabilitydetermination”,
andCRconformstoanimplementation-defined(IE011)rulethatcorrectlyinfersthat
thevalueofCRcannotbenull.
7.13
1. Rationale: Addmissingiterator.
ReplaceSyntaxRule18)f)with:
18) .
f) Forallk,1(one)≤k≤p,letDTPC bethedeclaredtypeofthecolumnidentifiedbyPC.
k k
7.14
1. Rationale: Removeincorrectreferencetoadescriptor.
ReplaceSyntaxRule1)with:
1) LetHCbethe.LetTEbethethatimmediatelycontains
HC.IfTEdoesnotimmediatelycontaina,then“GROUPBY()”isimplicit.
LetTbethetabledefinedbytheGBCimmediatelycontainedinTEandlet
RbetheresultofGBC.
7.16
1. Rationale: Correctlyidentifyimplementation-definedaspectsthataredependentonFeatureT101,
“Enhancednullabilitydetermination”,andremovetheduplicationofthoseaspects.
ReplaceSyntaxRule19)c)with:
19) .
c) IftheSQL-implementationsupportsFeatureT101,“Enhancednullabilitydetermination”,
andthereisanimplementation-defined(IE011)rulebywhichtheSQL-implementation
cancorrectlydeducethatthevalueofthecolumncannotbenull.
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
7.17
1. Rationale: Addmissingfunctiondefinition.
InsertthefollowingSyntaxRule:
3) .
j) .
vi.1) LetSSbethesetofsubscriptsoftheWQNinastratum.Letkbethenumberof
subscriptsinSS.Letsbeabijectivefunctionthatmapstheintegers{1,.,k}to
thesubscriptsinSS.
NOTE313.1—Thus,SS={s(1),.,s(k)}
8 Predicates
8.5
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutatleastoneofFeatureT042,“ExtendedLOBdatatypesupport”,orFeatureT022,
“AdvancedsupportforBINARYandVARBINARYdatatypes”,conformingSQLlanguageshall
notcontainan.
8.6
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureT141,“SIMILARpredicate”,conformingSQLlanguageshallnotcontaina
.
8.7
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureF841,“LIKE_REGEXpredicate”,conformingSQLlanguageshallnotcontain
a.
8.12
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
1) WithoutFeatureT061,“UCSsupport”,conformingSQLlanguageshallnotcontaina predicatepart2>.
8.13
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureF741,“ReferentialMATCHtypes”,conformingSQLlanguageshallnotcontain
a.
8.14
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureF053,“OVERLAPSpredicate”,conformingSQLlanguageshallnotcontainan
.
8.15
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureT151,“DISTINCTpredicate”,conformingSQLlanguageshallnotcontaina
.
NOTE3—TheConformanceRulesofSubclause9.11,“Equalityoperations”,alsoapply.
8.16
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureS271,“Basicmultisetsupport”,conformingSQLlanguageshallnotcontain
a.
NOTE4—TheConformanceRulesofSubclause9.11,“Equalityoperations”,alsoapply.
8.17
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureS275,“Advancedmultisetsupport”,conformingSQLlanguageshallnotcontain
a.
NOTE5—TheConformanceRulesofSubclause9.13,“Multisetelementgroupingoperations”,alsoapply.
©ISO/IEC2026–Allrightsreserved
ISO/IEC 9075-2:2023/Cor. 1:2026(en)
8.18
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureS271,“Basicmultisetsupport”,conformingSQLlanguageshallnotcontain
a.
NOTE6—TheConformanceRulesofSubclause9.13,“Multisetelementgroupingoperations”,alsoapply.
8.19
1. Rationale: CorrectthescopeofaConformanceRule.
ReplaceConformanceRule1)with:
1) WithoutFeatureS151,“Typepredicate”,conformingSQLlanguageshallnotcontaina predicatepart2>.
8.22
1. Rationale: CorrectthefeaturecodeinaConformanceRule.
ReplaceConformanceRule2)with:
2) WithoutFeatureT803,“String-basedJSON”,conformingSQLlanguageshallnotcontaina
thatsimplycontainsa.
9 Additionalcommonrules
9.2 Storeassignment
1. Rationale: Correctthetruncationofwhitespace.
ReplaceGeneralRule3)b)ii)with:
3) .
b) .
ii) IfthedeclaredtypeofTisfixed-lengthcharacterstringwithlengthincharacters
LandthelengthincharactersMofVislargerthanL,then
Case:
1) IftherightmostM−LcharactersofVareall
characters,thenthevalueofTissettothefirstLcharactersofV.
2) Otherwise,anexceptionconditionisraised:dataexception—stringdata,
righttruncation(22001).
©ISO/IEC2026
...