ISO/IEC 9075-1:1999/Cor 2:2003
(Corrigendum)Information technology — Database languages — SQL — Part 1: Framework (SQL/Framework) — Technical Corrigendum 2
Information technology — Database languages — SQL — Part 1: Framework (SQL/Framework) — Technical Corrigendum 2
Technologies de l'information — Langages de base de données — SQL — Partie 1: Charpente (SQL/Charpente) — Rectificatif technique 2
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-1:1999
TECHNICAL CORRIGENDUM 2
Published 2003-06-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Database languages — SQL —
Part 1:
Framework (SQL/Framework)
TECHNICAL CORRIGENDUM 2
Technologies de l'information — Langages de base de données — SQL —
Partie 1: Charpente (SQL/Charpente)
RECTIFICATIF TECHNIQUE 2
Technical Corrigendum 2 to ISO/IEC 9075-1:1999 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.
ISO/IEC 9075-1:1999/Cor. 2:2003 cancels and replaces ISO/IEC 9075-1:1999/Cor. 1:2000.
Statement of purpose for rationale:
A statement indicating the rationale for each change to ISO/IEC 9075 is included. This is to inform the users of
that standard as to the reason why it was judged necessary to change the original wording. In many cases the
reason is editorial or to clarify the wording; in some cases it is to correct an error or an omission in the original
wording.
Notes on numbering:
Where this Corrigendum introduces new Syntax, Access, General and Conformance Rules, the new rules have
been numbered as follows:
Rules inserted between, for example, Rules 7) and 8) are numbered 7.1), 7.2), etc. [or 7) a.1), 7) a.2), etc.]. Those
inserted before Rule 1) are numbered 0.1), 0.2), etc.
Where this Corrigendum introduces new Subclauses, the new subclauses have b een numbered as follows:
Subclauses inserted between, for example, Subclause 4.3.2 and 4.3.3 are numbered 4.3.2a, 4.3.2b, etc.
Those inserted before, for example, 4.3.1 are numbered 4.3.0, 4.3.0a, etc.
ICS 35.060 Ref. No. ISO/IEC 9075-1:1999/Cor.2:2003(E)
© ISO/IEC 2003 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9075-1:1999/Cor.2:2003(E)
Contents
Page
4.6.2.1 Ch aracter sets . . . . . . . 3
4.6.2.2 Collations . . . . . . . 3
4.8.2.3 Locators . . . . . . . 3
4.10.3 Built-in Functions . . . . . . 4
4.11.2 SQL-statements classified by function . . . . . 4
5.3.3 SQL-statem ents specified in ISO/IEC 9075-2 . . . . . 4
5.5.1 SQL-statem ents specified in ISO/IEC 9075-4 . . . . . 4
5.6.5.1 A dditional fun ctional classe s of SQL -statements . . . . . 5
6.1 Notation . . . . . . . 5
6.2.3.2 Syntactic containment . . . . . 5
6.2.3.4 Rule evaluation order . . . . . 6
6.2.5 Relationships of incremental parts to ISO/IEC 9075-2, Foundation . . . 6
6.3 O bject i dent ifi er for Da taba se Lan guage SQL . . . . . 9
Annex B SQL Packages . . . . 10
Annex B.5 CLI SQL . . . . . 10
Annex B .9 SQL/M M Supp ort . . . . 11
Annex C Implem entation-de fined eleme nts . . . 11
Annex D Implem entation-de penden t elements . . . 11
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9075-1:1999/Cor.2:2003(E)
Information technology — Database languages — SQL —
Part 1:
Framework (SQL/Framework)
TECHNICAL CORRIGENDUM 2
4.6.2.1 Character sets
1. Rationale: Clarify the distinction between character sets and character repertoires.
st
Replace the 1 paragraph with:
A character set has a named set of characters (character repertoire) that may be used for forming values of the
character data type, as well as a named character encoding form. Every character set has a default collation.
Character sets provided by the SQL-implementation, whether defined by other standards or by the SQL-
implementation, are represented in the Information Schema.
rd th th
Replace the 3 , 4 and 5 paragraphs with:
The character repertoire of every character set supported by an SQL-implementation is some subset of the
repertoire of the Universal Character Set specified by ISO/IEC 10646.
The notation specified in ISO/IEC 10646-1, Subclause 6.5, "Identifiers for characters", is the canonical
representation of characters and character strings in ISO/IEC 9075.
NOTE 3 – ISO/IEC 10646 assigns a range of code points for ‘‘private use’’. Future editions of ISO/IEC 10646 are likely
to add more code points, which SQL-implementations are required to support.
4.6.2.2 Collations
1. Rationale: Standardize terminology.
st
Replace the 1 paragraph with:
A collation is a named operation for ordering character strings in a particular character repertoire.
4.8.2.3 Locators
1. Rationale: Correct the specification of which locators are marked invalid when an SQL-transaction ends.
th
Replace the 8 paragraph with:
A non-h oldable loca tor remains v alid until the end of the SQL -transaction in which it w as genera ted, unless it
is explicitly made invalid by the execution of a or a that
specifies a is executed before the end of that SQL-transaction if the locator was generated
subsequent to the establishment of the savepoint identified by the .
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 3 ----------------------
ISO/IEC 9075-1:1999/Cor.2:2003(E)
th
Replace 9 paragraph with:
A holda ble locator m ay remain valid beyo nd the end of the SQL -transaction in which it is ge nerated. A
holdable locator becomes invalid whenever a identifying that locator is executed or
the SQL-transaction in which it is generated or any subsequent SQ L-transaction is rolled back. All locators
remaining valid at the end of an SQL-session are marked invalid when that SQL-session terminates.
4.10.3 Built-in Functions
1. Rationale: Clarify the semantics of built-in functions.
Delete the entire Subclause.
4.11.2 SQL-statements classified by function
1. Rationale: Correct the classification of SQL-statements.
st
Add a list element to the 1 paragraph:
— SQL-dynamic statements, which support the preparation and execution of dynamically generated SQL-
statements, and obtaining information about them.
5.3.3 SQL-statements specified in ISO/IEC 9075-2
1. Rationale: Correct the classification of SQL-statements.
th st
Replace the 4 bullet of the 1 paragraph with:
— Two SQL-control statements (CALL and RETURN ), which can be used to invoke a procedure and
specify a value to be returned by a function.
5.5.1 SQL-statements specified in ISO/IEC 9075-4
1. Rationale: Correct the classification of SQL-statements.
st st
Replace the 1 bullet of the 1 paragraph with:
— Additional SQL-control statements which may be used to control the execution of an SQL routine.
2. Rationale: Correct the classification of SQL-statements.
nd st
Delete the 2 bullet from the 1 paragraph
3. Rationale: Correct the classification of SQL-statements.
rd st
Replace the 3 bullet of the 1 paragraph with:
— Additional SQL-diagnostics statements, which may be used to signal exceptions.
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 9075-1:1999/Cor.2:2003(E)
4. Rationale: Correct the classification of SQL-statements.
st
Insert the following bullets to the 1 paragraph:
— SQL-control declaration statements which may be used to declare variables and exception handlers.
— Additional SQL-schema statements, which may be used to create and drop modules.
5.6.5.1 Additional functional classes of SQL-statements
1. Rationale: Correct the classification of SQL-statements.
st
Replace the bullet of the 1 paragraph with:
— SQL-dynamic statements, which support the preparation and execution of dynamically generated SQL-
statements, and obtaining information about them.
2. Rationale: Correct the classification of SQL-statements.
nd
Replace the 2 paragraph with:
A number of SQL-data statements are also added, most of which contain the word "dynamic" in their names.
They are not to be confused with SQL-dynamic statements.
6.1 Notation
1. Rationale: Define “left normal form derivation” for use in Subclause 14.1, “” in Part 1.
Insert the following paragraph at the end of the Subclause:
The left normal form derivation of a character string CS in the source language character set from a BNF non-
terminal NT is obtained by applying steps 1 through 5 above, to NT, always selecting in step 5 the leftmost
BNF n on-termina l.
6.2.3.2 Syntactic containment
1. Rationale: General containment must also recurse through s.
th
Replace the 8 paragraph with:
If contains a that identifies a view that is defined by a V, then is
said to generally c ontain the contained in V. If contains a that
identifies a QE, then is said to generally contain QE. If contains a
invocation> RI, then is said to generally c ontain the routine bodies of all s in the
set of subject routines of RI. If co ntains , then genera lly contains < B>. If genera lly
contains and generally contains , then generally contains .
© ISO/IEC 2003 – All rights reserved 5
---------------------- Page: 5 ----------------------
ISO/IEC 9075-1:1999/Cor.2:2003(E)
6.2.3.4 Rule evaluation order
1. Rationale: Define the term “intermediate results”.
Insert the following paragraph as the last paragraph of this Subclause:
During the com putation of the result of an expression, the S QL-implem entation may produ ce one or more
intermed iate results that are used in determinin g that result. Th e declared type of an inte rmediate res ult is
impleme ntation-dep endent.
6.2.5 Relationships of incremental parts to ISO/IEC 9075-2, Foundation
1. Rationale: To permit the modification of Parts 1, 3 and 10 as well as Parts 2 and 5 in other Parts, since Part
1 needs to be update d by the C onforma nce clause s of other Pa rts and Pa rts 3 and 10 are analo gous in
functionality to Part 5.
Replace the entire Subclause with:
6.2.5 Relationships of incremental parts within ISO/IEC 9075
Parts of ISO/IEC 9075 other than this part of ISO/IEC 9075 and ISO/IEC 9075-2 depend on ISO/IEC 9075-1,
ISO/IEC 907 5-2 and its Technical C orrigenda and are referenc ed as incremental parts. Eac h incremental part
is to be used as though it were merged with the text of ISO/IEC 9075. This Subclause describes the
conventions used to specify the merger.
The merger described also accounts for the Technical Corrigenda that have been published to correct ISO/IEC
9075. This accommodation is typically indicated by the presence of a phrase like “in the Technical
Corrigenda” or “in the TC”.
6.2.5.1 New and modified Clauses, Subclauses, and Annexes
Where a Clause (other than Clause 1, “Scope”, and Clause 2, “Normative references”), Subclause, or Annex
in any incremental part of ISO/IEC 9075 has a name identical to a Clause, Subclause, or Annex in ISO/IEC
9075-1, ISO/IEC 9075-2, ISO/IEC 9075-3, ISO/IEC 9075-5 or ISO/IEC 9075-10 (unless the incre mental part
is itself ISO/IEC 9075-3, ISO/IEC 9075-5 or ISO/IEC 9075-10), it supplements the Clause, Subclause, or
Annex, respectively, in ISO/IEC 9075-1 and/or ISO/IEC 9075-2 and/or ISO/IEC 9075-3 and/or ISO/IEC
9075-5 and/or ISO/IEC 9075-10, r
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.