ISO/IEC 9075-11:2016/Cor 2:2022
(Corrigendum)Information technology - Database languages - SQL - Part 11: Information and definition schemas (SQL/Schemata) - Technical Corrigendum 2
Information technology - Database languages - SQL - Part 11: Information and definition schemas (SQL/Schemata) - Technical Corrigendum 2
Technologies de l'information — Langages de base de données — SQL — Partie 11: Schémas des informations et des définitions (SQL/Schemata) — Rectificatif technique 2
General Information
- Status
- Published
- Publication Date
- 23-Jun-2022
- Technical Committee
- ISO/IEC JTC 1/SC 32 - Data management and interchange
- Drafting Committee
- ISO/IEC JTC 1/SC 32 - Data management and interchange
- Current Stage
- 9599 - Withdrawal of International Standard
- Start Date
- 01-Jun-2023
- Completion Date
- 30-Oct-2025
Relations
- Effective Date
- 11-Feb-2023
Overview
ISO/IEC 9075-11:2016/Cor 2:2022 is Technical Corrigendum 2 to Part 11 of the SQL standard (ISO/IEC 9075) - “Information and definition schemas (SQL/Schemata)”. Published June 2022 and prepared by ISO/IEC JTC 1/SC 32, this corrigendum issues targeted corrections and clarifications to the INFORMATION_SCHEMA and DEFINITION_SCHEMA metadata definitions used by SQL implementations. Corrections include revised view and table definitions, syntax fixes, updated conformance rules, and refined CHECK constraints.
Key topics and technical changes
- Corrected view definitions: Several INFORMATION_SCHEMA views are revised (for example, INFORMATION_SCHEMA_CATALOG_NAME, ROUTINE_ROUTINE_USAGE, ROUTINE_SEQUENCE_USAGE) with updated CREATE VIEW statements and SELECT lists to match intended semantics.
- Conformance rule updates: Multiple conformance rules were corrected, removed, or added - clarifying when specific INFORMATION_SCHEMA views must not be referenced depending on features (e.g., application-time period tables, trigger capability, polymorphic table functions).
- Parameter and private-parameter adjustments: The PARAMETERS and PRIVATE_PARAMETERS views had column references corrected and inappropriate column/ConformanceRule entries removed to better reflect polymorphic/function parameter behavior.
- Definition-schema table fixes: The DATA_TYPE_DESCRIPTOR base table and CHARACTER_REPERTOIRES population rules were corrected - including syntax, CHECK constraints, and allowable DATA_TYPE combinations.
- Security / grant statements: Some view definitions explicitly include GRANT SELECT ON ... TO PUBLIC WITH GRANT OPTION to clarify intended access for standardized metadata views.
- Cross-references: This corrigendum modifies or harmonizes subclauses that interact with other SQL parts (e.g., ISO/IEC 9075-4, -9, -13, -14, -15).
Practical applications - who should use this standard
- DBMS implementers and vendors: Use the corrigendum to update metadata view/table implementations so INFORMATION_SCHEMA and DEFINITION_SCHEMA conform to the corrected SQL standard.
- SQL tooling and migration vendors: Ensure metadata discovery, tooling, and compliance tests reflect corrected column names, constraints, and conformance rules.
- DBAs and architects: Rely on updated metadata definitions when writing portable SQL metadata queries or designing cross-vendor catalogs.
- Standards bodies and auditors: Use the corrigendum to clarify conformance assessments, test suites, and interoperability specifications.
Related standards
- ISO/IEC 9075 (SQL) family - particularly Parts referenced in the corrigendum: 9075-4, -9, -13, -14, -15 (these parts contain related subclauses modified by this Corrigendum).
Keywords: ISO/IEC 9075-11:2016/Cor 2:2022, SQL/Schemata, INFORMATION_SCHEMA, DEFINITION_SCHEMA, SQL corrigendum, database metadata, DATA_TYPE_DESCRIPTOR, SQL conformance.
Frequently Asked Questions
ISO/IEC 9075-11:2016/Cor 2:2022 is a standard published by the International Organization for Standardization (ISO). Its full title is "Information technology - Database languages - SQL - Part 11: Information and definition schemas (SQL/Schemata) - Technical Corrigendum 2". This standard covers: Information technology - Database languages - SQL - Part 11: Information and definition schemas (SQL/Schemata) - Technical Corrigendum 2
Information technology - Database languages - SQL - Part 11: Information and definition schemas (SQL/Schemata) - Technical Corrigendum 2
ISO/IEC 9075-11:2016/Cor 2:2022 is classified under the following ICS (International Classification for Standards) categories: 35.060 - Languages used in information technology. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO/IEC 9075-11:2016/Cor 2:2022 has the following relationships with other standards: It is inter standard links to ISO/IEC 9075-11:2023. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
ISO/IEC 9075-11:2016/Cor 2:2022 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-11:2016
TECHNICAL CORRIGENDUM 2
Published 2022-06
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Database languages — SQL — Part 11:
Information and definition schemas (SQL/Schemata)
TECHNICAL CORRIGENDUM 2
Technologies de l'information — Langages de base de données — SQL — Partie 11: Schémas des
informations et des définitions (SQL/Schemata)
RECTIFICATIF TECHNIQUE 2
Technical Corrigendum 2 to ISO/IEC 9075-11:2016 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.
ICS 35.060 Ref. No. ISO/IEC 9075-11:2016/Cor.2:2022(E)
© ISO/IEC 2022 – All rights reserved
Published in Switzerland
ISO/IEC9075-11:2016/Cor.2:2022(E)
5 InformationSchema
5.2 INFORMATION_SCHEMA_CATALOG_NAMEview
1. Rationale:Correctthesyntax.
Replacetheviewdefinitionwith:
CREATE VIEW INFORMATION_SCHEMA_CATALOG_NAME AS
SELECT CATALOG_NAME
FROM DEFINITION_SCHEMA.CATALOG_NAME
WHERE CATALOG_NAME = 'CN';
5.34 KEY_PERIOD_USAGEview
1. Rationale:CorrectaConformanceRule.
ReplaceConformanceRule2)with:
2) WithoutFeatureT181,“Application-timeperiodtables”,conformingSQLlanguageshallnot
referencetheviewINFORMATION_SCHEMA.KEY_PERIOD_USAGE.
5.37 PARAMETERSview
ThisSubclauseismodifiedbySubclause19.5,“PARAMETERSview”,inISO/IEC9075-4.
ThisSubclauseismodifiedbySubclause21.10,“PARAMETERSview”,inISO/IEC9075-14.
1. Rationale:Identifythecorrectcolumn.
ReplaceConformanceRule4)with:
4) WithoutFeatureB200,“Polymorphictablefunctions”,conformingSQLlanguageshallnotrefer-
enceINFORMATION_SCHEMA.PARAMETERS.TABLE_SEMANTICS,INFORMA-
TION_SCHEMA.PARAMETERS.IS_PRUNABLE,orINFORMATION_SCHEMA.PARAME-
TERS.HAS_PASS_THROUGH_COLUMNS.
2. Rationale:RemoveincorrectandmisleadingConformanceRules.
DeleteConformanceRules5)and6).
5.39 PRIVATE_PARAMETERSview
1. Rationale:Removeincorrectandinappropriatecolumnreferences.
IntheDefinition,delete"P.FROM_SQL_SPECIFIC_CATALOG,P.FROM_SQL_SPECIFIC_SCHEMA,
P.FROM_SQL_SPECIFIC_NAME,P.TO_SQL_SPECIFIC_CATALOG,P.TO_SQL_SPECIFIC_SCHEMA,
P.TO_SQL_SPECIFIC_NAME,"and"DTD.TABLE_SEMANTICS,DTD.IS_PRUNABLE,
DTD.HAS_PASS_THROUGH_COLUMNS"fromtheselectlist.
2 © ISO/IEC 2022 – All rights reserved
ISO/IEC9075-11:2016/Cor.2:2022(E)
2. Rationale:Privateparametersofapolymorphictablefunctioncannotbegenerictables.
DeleteConformanceRules5),6)and7).
5.51 ROUTINE_ROUTINE_USAGEview
1. Rationale:Clarifythecontentsofcolumns.
ReplacetheDefinitionwith:
Definition
CREATE VIEW ROUTINE_ROUTINE_USAGE AS
SELECT RRU.SPECIFIC_CATALOG, RRU.SPECIFIC_SCHEMA, RRU.SPECIFIC_NAME,
RRU.SUBJECT_ROUTINE_CATALOG AS ROUTINE_CATALOG,
RRU.SUBJECT_ROUTINE_SCHEMA AS ROUTINE_SCHEMA,
RRU.SUBJECT_ROUTINE_NAME AS ROUTINE_NAME
FROM DEFINITION_SCHEMA.ROUTINE_ROUTINE_USAGE AS RRU
JOIN
DEFINITION_SCHEMA.SCHEMATA AS S
ON ( ( RRU.SUBJECT_ROUTINE_CATALOG, RRU.SUBJECT_ROUTINE_SCHEMA )
= ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
WHERE ( S.SCHEMA_OWNER = CURRENT_USER
OR
S.SCHEMA_OWNER IN
( SELECT ER.ROLE_NAME
FROM ENABLED_ROLES AS ER ) )
AND
RRU.SPECIFIC_CATALOG
= ( SELECT ISCN.CATALOG_NAME
FROM INFORMATION_SCHEMA_CATALOG_NAME AS ISCN );
GRANT SELECT ON TABLE ROUTINE_ROUTINE_USAGE
TO PUBLIC WITH GRANT OPTION;
NOTE1—ThecolumnsROUTINE_CATALOG,ROUTINE_SCHEMA,andROUTINE_NAMEoftheviewidentifythesubject
routineofeithera,a,a,ora
containedintheorintheofanSQLparameterofanSQL-invokedroutine.
5.52 ROUTINE_SEQUENCE_USAGEview
1. Rationale:Makethedefinitionoftheviewmatchitsdescription.
ReplacetheDefinitionwith:
CREATE VIEW ROUTINE_SEQUENCE_USAGE AS
SELECT SPECIFIC_CATALOG, SPECIFIC_SCHEMA, SPECIFIC_NAME,
R.ROUTINE_CATALOG, R.ROUTINE_SCHEMA, R.ROUTINE_NAME,
RSU.SEQUENCE_CATALOG, RSU.SEQUENCE_SCHEMA, RSU.SEQUENCE_NAME
FROM ( DEFINITION_SCHEMA.SEQENCE_SEQUENCE_USAGE AS RSU
© ISO/IEC 2022 – All rights reserved 3
ISO/IEC9075-11:2016/Cor.2:2022(E)
JOIN
DEFINITION_SCHEMA.ROUTINES AS R
USING ( SPECIFIC_CATALOG, SPECIFIC_SCHEMA, SPECIFIC_NAME ) )
JOIN
DEFINITION_SCHEMA.SCHEMATA AS S
ON ( ( RSU.SEQUENCE_CATALOG, RSU.SEQUENCE_SCHEMA )
= ( S.CATALOG_NAME, S.SCHEMA_NAME ) )
WHERE ( S.SCHEMA_OWNER = CURRENT_USER
OR
S.SCHEMA_OWNER IN
( SELECT ER.ROLE_NAME
FROM ENABLED_ROLES AS ER ) )
AND
SPECIFIC_CATALOG
= ( SELECT ISCN.CATALOG_NAME
FROM INFORMATION_SCHEMA_CATALOG_NAME AS ISCN );
GRANT SELECT ON TABLE ROUTINE_SEQUENCE_USAGE
TO PUBLIC WITH GRANT OPTION;
5.69 TRIGGER_PERIOD_USAGEview
1. Rationale:AddmissingConformanceRule.
AddthefollowingConformanceRule:
5) WithoutFeatureT211,“Basictriggercapability”,conformingSQLlanguageshallnotreference
theviewINFORMATION_SCHEMA.TRIGGER_PERIOD_USAGE.
5.78 VIEW_PERIOD_USAGEview
1. Rationale:DeleteincorrectConformanceRule.
DeleteConformanceRule2).
5.82 Shortnameviews
ThisSubclauseismodifiedbySubclause19.8,“Shortnameviews”,inISO/IEC9075-4.
ThisSubclauseismodifiedbySubclause24.14,“Shortnameviews”,inISO/IEC9075-9.
ThisSubclauseismodifiedbySubclause14.7,“Shortnameviews”,inISO/IEC9075-13.
ThisSubclauseismodifiedbySubclause21.15,“Shortnameviews”,inISO/IEC9075-14.
1. Rationale:Removeincorrectcolumnreferences.
IntheDefinition,delete"FROM_SQL_SPEC_CAT,FROM_SQL_SPEC_SCH,FROM_SQL_SPEC_NAME,
TO_SQL_SPEC_CAT,TO_SQL_SPEC_SCHEMA,TO_SQL_SPEC_NAME,"and",TABLE_SEMANTICS,
IS_PRUNABLE,HAS_PASS_THRU_COLS"fromtheviewcolumnlistofPRIVATE_PARAMS_S,anddelete
"FROM_SQL_SPECIFIC_CATALOG,FROM_SQL_SPECIFIC_SCHEMA,FROM_SQL_SPECIFIC_NAME,
TO_SQL_SPECIFIC_CATALOG,TO_SQL_SPECIFIC_SCHEMA,TO_SQL_SPECIFIC_NAME,"and",
TABLE_SEMANTICS,IS_PRUNABLE,HAS_PASS_THROUGH_COLUMNS"fromtheselectlistof
PRIVATE_PARAMS_S.
4 © ISO/IEC 2022 – All rights reserved
ISO/IEC9075-11:2016/Cor.2:2022(E)
2. Rationale:Makethedefinitionoftheviewmatchitsdescription.
ReplacetheDefinitionoftheROUT_SEQ_USAGE_Sviewwith:
CREATE VIEW ROUT_SEQ_USAGE_S
( SPECIFIC_CATALOG, SPECIFIC_SCHEMA, SPECIFIC_NAME,
ROUTINE_CATALOG, ROUTINE_SCHEMA, ROUTINE_NAME,
SEQUENCE_CATALOG, SEQUENCE_SCHEMA, SEQUENCE_NAME ) AS
SELECT SPECIFIC_CATALOG, SPECIFIC_SCHEMA, SPECIFIC_NAME,
ROUTINE_CATALOG, ROUTINE_SCHEMA, ROUTINE_NAME,
SEQUENCE_CATALOG, SEQUENCE_SCHEMA, SEQUENCE_NAME
FROM INFORMATION_SCHEMA.ROUTINE_SEQUENCE_USAGE;
3. Rationale:RemoveincorrectandmisleadingConformanceRules:
DeleteConformanceRules69),70),and73).
4. Rationale:AddmissingConformanceRules:
InsertthefollowingConformanceRules:
74) WithoutFeatureT522,“DefaultvaluesforINparametersofSQL-invokedprocedures”,Feature
T523,“DefaultvaluesforINOUTparametersofSQL-invokedprocedures”,orFeatureT525,
“DefaultvaluesforparametersofSQL-invokedfunctions”,conformingSQLlanguageshallnot
referenceINFORMATION_SCHEMA.PRIVATE_PARAMS_S.PARAMETER_DEFAULT.
75) WithoutFeatureF651,“Catalognamequalifiers”,conformingSQLlanguageshallnotreference
theviewINFORMATION_SCHEMA.CATALOG_NAME.
76) WithoutFeatureF690,“Collationsupport”,conformingSQLlanguageshallnotreferencethe
viewINFORMATION_SCHEMA.COLLATION_APPLIC_S.
77) WithoutFeatureF341,“Usagetables”,conformingSQLlanguageshallnotreferencetheview
INFORMATION_SCHEMA.CONSTR_PER_USAGE.
78) WithoutFeatureT181,“Application-timeperiodtables”,conformingSQLlanguageshallnot
referencetheviewINFORMATION_SCHEMA.CONSTR_PER_USAGE.
79) WithoutFeatureF341,“Usagetables”,conformingSQLlanguageshallnotreferencetheview
INFORMATION_SCHEMA.ROUTINE_PERIOD_USAGE.
80) WithoutFeatureT180,“System-versionedtables”,conformingSQLlanguageshallnotreference
theviewINFORMATION_SCHEMA.ROUTINE_PER_USAGE.
81) WithoutFeatureT181,“Application-timeperiodtables”,conformingSQLlanguageshallnot
referencetheviewINFORMATION_SCHEMA.ROUTINE_PER_USAGE.
82) WithoutFeatureF341,“Usagetables”,conformingSQLlanguageshallnotreferencetheview
INFORMATION_SCHEMA.TRIG_PER_USAGE.
83) WithoutFeatureT180,“System-versionedtables”,conformingSQLlanguageshallnotreference
theviewINFORMATION_SCHEMA.TRIG_PER_USAGE.
© ISO/IEC 2022 – All rights reserved 5
ISO/IEC9075-11:2016/Cor.2:2022(E)
84) WithoutFeatureT181,“Application-timeperiodtables”,conformingSQLlanguageshallnot
referencetheviewINFORMATION_SCHEMA.TRIG_PER_USAGE.
6 DefinitionSchema
6.10 CHARACTER_REPERTOIRESbasetable
1. Rationale:CorrectthedefinitionoftheTablePopulation.
ReplaceTablePopulationrule4)b)iv)with:
4) .
b) .
iv) UCS:'UCS'andanimplementation-definedchoiceofeither'UCS_BASIC'or'UNICODE'.
2. Rationale:CorrectthedefinitionoftheTablePopulation.
DeleteTablePopulationrules4)b)v)and4)b)vi).
6.22 DATA_TYPE_DESCRIPTORbasetable
ThisSubclauseismodifiedbySubclause25.2,“DATA_TYPE_DESCRIPTORbasetable”,inISO/IEC9075-9.
ThisSubclauseismodifiedbySubclause22.1,“DATA_TYPE_DESCRIPTORbasetable”,inISO/IEC9075-14.
ThisSubclauseismodifiedbySubclause20.1,“DATA_TYPE_DESCRIPTORbasetable”,inISO/IEC9075-15.
1. Rationale:Correctthesyntax.
Replacetheviewdefinitionwith:
CREATE TABLE DATA_TYPE_DESCRIPTOR (
OBJECT_CATALOG INFORMATION_SCHEMA.SQL_IDENTIFIER,
OBJECT_SCHEMA INFORMATION_SCHEMA.SQL_IDENTIFIER,
OBJECT_NAME INFORMATION_SCHEMA.SQL_IDENTIFIER,
OBJECT_TYPE INFORMATION_SCHEMA.CHARACTER_DATA
CONSTRAINT DATA_TYPE_DESCRIPTOR_CHECK_OBJECT_TYPE
CHECK ( OBJECT_TYPE IN
( 'TABLE', 'DOMAIN', 'USER-DEFINED TYPE',
'ROUTINE', 'SEQUENCE' ) ),
DTD_IDENTIFIER INFORMATION_SCHEMA.SQL_IDENTIFIER,
DATA_TYPE INFORMATION_SCHEMA.CHARACTER_DATA
CONSTRAINT DATA_TYPE_DESCRIPTOR_OBJECT_DATA_TYPE_NOT_NULL
NOT NULL,
CHARACTER_SET_CATALOG INFORMATION_SCHEMA.SQL_IDENTIFIER,
CHARACTER_SET_SCHEMA INFORMATION_SCHEMA.SQL_IDENTIFIER,
CHARACTER_SET_NAME INFORMATION_SCHEMA.SQL_IDENTIFIER,
CHARACTER_MAXIMUM_LENGTH INFORMATION_SCHEMA.CARDINAL_NUMBER,
CHARACTER_OCTET_LENGTH INFORMATION_SCHEMA.CARDINAL_NUMBER,
COLLATION_CATALOG INFORMATION_SCHEMA.SQL_IDENTIFIER,
COLLATION_SCHEMA INFORMATION_SCHEMA.SQL_IDENTIFIER,
6 © ISO/IEC 2022 – All rights reserved
ISO/IEC9075-11:2016/Cor.2:2022(E)
COLLATION_NAME INFORMATION_SCHEMA.SQL_IDENTIFIER,
NUMERIC_PRECISION INFORMATION_SCHEMA.CARDINAL_NUMBER,
NUMERIC_PRECISION_RADIX INFORMATION_SCHEMA.CARDINAL_NUMBER,
NUMERIC_SCALE INFORMATION_SCHEMA.CARDINAL_NUMBER,
DECLARED_DATA_TYPE INFORMATION_SCHEMA.CHARACTER_DATA,
DECLARED_NUMERIC_PRECISION INFORMATION_SCHEMA.CARDINAL_NUMBER,
DECLARED_NUMERIC_SCALE INFORMATION_SCHEMA.CARDINAL_NUMBER,
DATETIME_PRECISION INFORMATION_SCHEMA.CARDINAL_NUMBER,
INTERVAL_TYPE INFORMATION_SCHEMA.CHARACTER_DATA,
INTERVAL_PRECISION INFORMATION_SCHEMA.CARDINAL_NUMBER,
USER_DEFINED_TYPE_CATALOG INFORMATION_SCHEMA.SQL_IDENTIFIER,
USER_DEFINED_TYPE_SCHEMA INFORMATION_SCHEMA.SQL_IDENTIFIER,
USER_DEFINED_TYPE_NAME INFORMATION_SCHEMA.SQL_IDENTIFIER,
SCOPE_CATALOG INFORMATION_SCHEMA.SQL_IDENTIFIER,
SCOPE_SCHEMA INFORMATION_SCHEMA.SQL_IDENTIFIER,
SCOPE_NAME INFORMATION_SCHEMA.SQL_IDENTIFIER,
MAXIMUM_CARDINALITY INFORMATION_SCHEMA.CARDINAL_NUMBER,
TABLE_SEMANTICS INFORMATION_SCHEMA.CHARACTER_DATA
CONSTRAINT DATA_TYPE_DESCRIPTOR_TABLE_SEMANTICS_CHECK
CHECK ( TABLE_SEMANTICS IN ( 'ROW', 'SET' ) ),
IS_PRUNABLE INFORMATION_SCHEMA.YES_OR_NO,
HAS_PASS_THROUGH_COLUMNS INFORMATION_SCHEMA.YES_OR_NO,
CONSTRAINT DATA_TYPE_DESCRIPTOR_DATA_TYPE_CHECK_COMBINATIONS
CHECK ( ( DATA_TYPE IN
( 'CHARACTER', 'CHARACTER VARYING', 'CHARACTER LARGE OBJECT' )
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME ) IS NOT NULL
AND
( CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH ) IS NOT NULL
AND
( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
DECLARED_DATA_TYPE, DECLARED_NUMERIC_PRECISION,
DECLARED_NUMERIC_SCALE ) IS NULL
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE IN
( 'BINARY', 'BINARY VARYING', 'BINARY LARGE OBJECT' )
AND
( CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH ) IS NOT NULL
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, COLLATION_CATALOG,
COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
© ISO/IEC 2022 – All rights reserved 7
ISO/IEC9075-11:2016/Cor.2:2022(E)
AND
( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
DECLARED_DATA_TYPE, DECLARED_NUMERIC_PRECISION,
DECLARED_NUMERIC_SCALE ) IS NULL
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE IN
( 'SMALLINT', 'INTEGER', 'BIGINT' )
AND
DECLARED_DATA_TYPE IN
( 'SMALLINT', 'INTEGER', 'BIGINT', 'NUMERIC', 'DECIMAL' )
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
NUMERIC_PRECISION_RADIX IN ( 2, 10 )
AND
NUMERIC_PRECISION IS NOT NULL
AND
NUMERIC_SCALE = 0
AND
( DECLARED_NUMERIC_SCALE IS NULL OR DECLARED_NUMERIC_SCALE = 0 )
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE IN
( 'NUMERIC', 'DECIMAL' )
AND
DECLARED_DATA_TYPE IN
( 'SMALLINT', 'INTEGER', 'BIGINT', 'NUMERIC', 'DECIMAL' )
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
8 © ISO/IEC 2022 – All rights reserved
ISO/IEC9075-11:2016/Cor.2:2022(E)
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
NUMERIC_PRECISION_RADIX = 10
AND
( NUMERIC_PRECISION, NUMERIC_SCALE ) IS NOT NULL
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE IN
( 'REAL', 'DOUBLE PRECISION', 'FLOAT' )
AND
DECLARED_DATA_TYPE IN
( 'REAL', 'DOUBLE PRECISION', 'FLOAT' )
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
NUMERIC_PRECISION IS NOT NULL
AND
NUMERIC_PRECISION_RADIX = 2
AND
NUMERIC_SCALE IS NULL
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE = 'DECFLOAT'
AND
DECLARED_DATA_TYPE = 'DECFLOAT'
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
© ISO/IEC 2022 – All rights reserved 9
ISO/IEC9075-11:2016/Cor.2:2022(E)
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
NUMERIC_PRECISION IS NOT NULL
AND
NUMERIC_PRECISION_RADIX = 10
AND
NUMERIC_SCALE IS NULL
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE IN
( 'DATE', 'TIME', 'TIMESTAMP',
'TIME WITH TIME ZONE', 'TIMESTAMP WITH TIME ZONE' )
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
DECLARED_DATA_TYPE, DECLARED_NUMERIC_PRECISION,
DECLARED_NUMERIC_SCALE ) IS NULL
AND
DATETIME_PRECISION IS NOT NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE = 'INTERVAL'
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
DECLARED_DATA_TYPE, DECLARED_NUMERIC_PRECISION,
10 © ISO/IEC 2022 – All rights reserved
ISO/IEC9075-11:2016/Cor.2:2022(E)
DECLARED_NUMERIC_SCALE ) IS NULL
AND
DATETIME_PRECISION IS NOT NULL
AND
INTERVAL_TYPE IN
( 'YEAR', 'MONTH', 'DAY', 'HOUR', 'MINUTE', 'SECOND',
'YEAR TO MONTH', 'DAY TO HOUR', 'DAY TO MINUTE',
'DAY TO SECOND', 'HOUR TO MINUTE',
'HOUR TO SECOND', 'MINUTE TO SECOND' )
AND
INTERVAL_PRECISION IS NOT NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE = 'BOOLEAN'
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, CHARACTER_MAXIMUM_LENGTH, CHARACTER_OCTET_LENGTH,
COLLATION_CATALOG, COLLATION_SCHEMA, COLLATION_NAME ) IS NULL
AND
( NUMERIC_PRECISION, NUMERIC_PRECISION_RADIX, NUMERIC_SCALE,
DECLARED_DATA_TYPE, DECLARED_NUMERIC_PRECISION,
DECLARED_NUMERIC_SCALE ) IS NULL
AND
DATETIME_PRECISION IS NULL
AND
( INTERVAL_TYPE, INTERVAL_PRECISION ) IS NULL
AND
( USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME ) IS NULL
AND
( SCOPE_CATALOG, SCOPE_SCHEMA, SCOPE_NAME ) IS NULL
AND
MAXIMUM_CARDINALITY IS NULL
AND
( TABLE_SEMANTICS, IS_PRUNABLE, HAS_PASS_THROUGH_COLUMNS ) IS NULL )
OR
( DATA_TYPE = 'USER-DEFINED'
AND
( CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
...










Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...