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

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: +41 22 749 01 11
Email: copyright@iso.org
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
...