ISO/IEC 9075-1:2003/Cor 1:2005
(Corrigendum)Information technology — Database languages — SQL — Part 1: Framework (SQL/Framework) — Technical Corrigendum 1
Information technology — Database languages — SQL — Part 1: Framework (SQL/Framework) — Technical Corrigendum 1
Technologies de l'information — Langages de base de données — SQL — Partie 1: Charpente (SQL/charpente) — Rectificatif technique 1
General Information
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-1:2003
TECHNICAL CORRIGENDUM 1
Published 2005-11-15
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 1
Technologies de l'information — Langages de base de données — SQL —
Partie 1: Charpente (SQL/charpente)
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to ISO/IEC 9075-1:2003 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.
Statement of purpose for rationale
A statement indicating the rationale for each change to ISO/IEC 9075-1:2003 is included. This is to inform the users of
ISO/IEC 9075-1:2003 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 Technical 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 Technical Corrigendum introduces new subclauses, the new subclauses have been numbered as follows:
Subclauses inserted between, for example, 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:2003/Cor.1:2005(E)
© ISO/IEC 2005 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9075-1:2003/Cor.1:2005(E)
ii © ISO/IEC 2005 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9075-1:2003/Cor.1:2005(E)
Contents Page
Foreword. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3 Definitions and use of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3.1.1 Definitions provided in this standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.2 SQL-environments and their components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.2.5a Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
4.6 SQL-schema objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4.6.13 Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
6 Notation and conventions used in other parts of ISO/IEC 9075 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
6.3 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
6.3.3 Use of terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
6.3.3.8 General Rules not terminated on exception conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
6.3.5 Relationships of parts within ISO/IEC 9075. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6.3.5.1 New and modified Clauses, Subclauses, and Annexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6.3.5.5 New and modified tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.3.5a Subclauses used as subroutines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
© ISO/IEC 2005 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 9075-1:2003/Cor.1:2005(E)
Information technology — Database languages — SQL —
Part 1:
Framework (SQL/Framework)
TECHNICAL CORRIGENDUM 1
Foreword
1. Rationale:Remove incorrect reference to obsolete part.
th th
In the 7 paragraph, delete the 5 bullet.
3 Definitions and use of terms
3.1.1 Definitions provided in this standard
1. Rationale:Delete an erroneous definition.
Delete definition 3.1.1.18
4 Concepts
4.2 SQL-environments and their components
4.2.5a Roles
1. Rationale:A role is not a schema object, nor is it a collection of role authorizations therefore the description
of roles is moved from subclause 4.6.13 to subclause 4.2.5a.
© ISO/IEC 2005 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 9075-1:2003/Cor.1:2005(E)
Insert the following Subclause:
4.2.5a Roles
A role is a potential grantee and grantor of privileges and other roles. A role can also own schemas and
other objects.
A role authorization permits a grantee (see Subclause 4.6.12, “Privileges”) to use every privilege granted
to the role. It also indicates whether the role authorization is grantable, in which case the grantee is authorized
to grant the role, to revoke a grant of the role, and to destroy the role.
4.6 SQL-schema objects
4.6.13 Roles
1. Rationale:A role is not a schema object, nor is it a collection of role authorizations; therefore the description
of roles is moved from subclause 4.6.13 to subclause 4.2.5a.
Delete the entire Subclause.
6 Notation and conventions used in other parts of ISO/IEC 9075
6.3 Conventions
6.3.3 Use of terms
6.3.3.8 General Rules not terminated on exception conditions
1. Rationale:Trigger execution continues after an exception.
nd rd
Insert the following item between the 2 and 3 items:
— Subclause 14.27, “Execution of triggers”, in ISO/IEC 9075-2.
2 © ISO/IEC 2005 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 9075-1:2003/Cor.1:2005(E)
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.