Information technology — Database languages — SQL — Part 2: Foundation (SQL/Foundation) — Technical Corrigendum 1

Technologies de l'information — Langages de base de données — SQL — Partie 2: Fondations (SQL/Fondations) — Rectificatif technique 1

General Information

Status
Withdrawn
Publication Date
20-Dec-2000
Withdrawal Date
20-Dec-2000
Current Stage
9599 - Withdrawal of International Standard
Completion Date
05-Jun-2003
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 9075-2:1999/Cor 1:2000
English language
211 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL STANDARD ISO/IEC 9075-1:1999
ISO/IEC 9075-2:1999
ISO/IEC 9075-3:1999
ISO/IEC 9075-4:1999
ISO/IEC 9075-5:1999
TECHNICAL CORRIGENDUM 1
Published 2000-12-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)
Part 2: Foundation (SQL/Foundation)
Part 3: Call-Level Interface (SQL/CLI)
Part 4: Persistent Stored Modules (SQL/PSM)
Part 5: Host Language Bindings (SQL/Bindings)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données — SQL —
Partie 1: Charpente (SQL/Charpente)
Partie 2: Fondations (SQL/Fondations)
Partie 3: Interface de niveau d'appel (SQL/CLI)
Partie 4: Modules stockés persistants (SQL/PSM)
Partie 5: Liants de langage d'hôte (SQL/Liants)
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to parts 1 to 5 of International Standard ISO/IEC 9075:1999 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 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 been 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 (parts 1 to 5):1999/Cor.1:2000(E)
© ISO/IEC 2000 – All rights reserved
Printed in Switzerland

---------------------- Page: 1 ----------------------
ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E)
Page
ISO/IEC 9075-1:1999
Database Languages - SQL-Part 1:Framework . 9
4.8.2.3 Locators . 9
4.11.2 SQL-statements classified by function . 9
5.3.3 SQL-statements specified in ISO/IEC 9075-2 . 9
5.5.1 SQL-statements specified in ISO/IEC 9075-4 . 9
5.6.5.1 Additional functional classes of SQL-statements . 10
6.2.5 Relationships of incremental parts to ISO/IEC 9075-2, Foundation . 10
Annex B SQL Packages . 13
Annex B.9 SQL/MM Support . 13
ISO/IEC 9075-2:1999
Database Languages - SQL-Part 2:Foundation . 15
3.1.1 Definitions taken from ISO/IEC 10646 . 15
3.1.2 Definitions taken from Unicode . 15
3.1.5 Definitions provided in Part 2 . 15
4.1 Data types . 17
4.2.1 Character strings and collating sequences . 19
4.2.4 Named character sets . 19
4.3.1 Binary string comparison . 20
4.4.1 Bit string comparison and assignment . 20
4.7.1 Datetimes . 20
4.7.3 “Operations involving datetimes and intervals” . 21
4.8 User-defined types . 21
4.8.1 Observers and mutators . 22
4.8.2 Constructors . 22
4.8.4 User-defined type comparison and assignment . 23
4.10 Reference types . 23
4.13 Data conversions . 24
4.16 Tables . 24
4.16.3 Operations involving tables . 25
4.18.1 General rules and definitions . 25
4.18.9 Known functional dependencies in the result of . 26
4.20 SQL-schemas . 26
4.21 SQL-client modules . 26
4.23 SQL-invoked routines . 26
4.24 Built-in functions . 29
4.25 SQL-paths . 29
4.26.4 Locators . 30
4.30.1 Classes of SQL-statements . 30
4.30.2 SQL-statements classified by functions . 30
4.30.3 SQL-statements and transaction states . 31
4.30.4 SQL-statement atomicity . 32
4.31.1 Authorization identifiers . 32
4.34.1 Execution contexts . 32
4.35.2 Execution of triggers . 33
5.2 and . 33
5.3 . 36
5.4 Names and identifiers . 36
6.1 . 37
6.3 and . 37
6.5 . 38
6.11 . 39
2 ©  ISO/IEC 2000 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E)
6.16 . 40
6.18 . 41
6.20 . 45
6.22 . 45
6.23 . 47
6.24 . 48
6.25 . 49
6.26 . 49
6.27 . 50
6.30 . 51
7.1 . 52
7.3 . 52
7.6

. 53
7.7 . 57
7.8 . 57
7.9 . 57
7.10 . 64
7.11 . 65
7.12 . 66
8.2 . 66
8.3 . 67
8.4 . 68
8.6 . 68
8.8 . 69
8.10 . 69
8.11 . 70
8.12 . 70
8.13 . 70
9.0 Determination of identical values . 71
9.1 Retrieval assignment . 72
9.3 Data types of results of aggregations . 72
10.4 . 73
10.5 . 77
10.6 . 78
10.7 . 78
10.12 Execution of triggers . 80
10.13 Execution of array-returning functions . 81
11.1 . 82
11.2 . 83
11.3
. 83
11.4 . 85
11.7 . 85
11.8 . 86
11.17 . 86
11.21 . 86
11.30 . 87
11.31 . 88
11.38 . 88
11.40 . 89
11.41 . 97
11.43 . 98
11.44 . 98
11.45 . 98
11.46 . 102
11.47 . 104
  ©  ISO/IEC 2000 – All rights reserved 3

---------------------- Page: 3 ----------------------
ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E)
11.48 . 108
11.49 . 108
11.50 . 114
11.51 . 114
11.52 . 115
11.54 . 116
11.55 . 117
11.56 . 119
11.57 . 119
12.2 . 119
12.4 . 120 12.6 . 120 13.1 . 121 13.2 . 121 13.3 . 121 13.5 . 121 14.1 . 122 14.3 . 124 14.5 . 124
14.6 . 125
14.8 . 126
14.9 . 127
14.10 . 127
14.11 . 128
14.18 Effect of inserting a table into a derived table . 128
15.2 . 128
16.4 . 128
16.5 . 128
16.7 . 129
19.1 . 129
20.11 ATTRIBUTES view . 130
20.18 COLUMNS view . 131
20.19 CONSTRAINT_COLUMN_USAGE view . 132
20.21 DATA_TYPE_PRIVILEGES view . 133
20.26 DOMAINS view . 133
20.27 ELEMENT_TYPES view . 134
20.29 FIELDS view . 134
20.31 METHOD_SPECIFICATION_PARAMETERS view . 135
20.32 METHOD_SPECIFICATIONS view . 135
20.33 PARAMETERS view . 136
20.34 REFERENCED_TYPES view . 136
20.38 ROLE_TABLE_GRANTS view . 137
20.56 TABLES view . 137
20.62 TRIGGERS view . 138
20.68 VIEWS view . 140
20.69 Short name views . 141
21.3 EQUAL_KEY_DEGREES assertion . 143
21.6 ASSERTIONS base table . 144
21.7 ATTRIBUTES base table . 144
21.8 CHARACTER_SETS base table . 144
21.12 COLLATIONS base table . 145
21.14 COLUMNS base table . 145
21.15 DATA_TYPE_DESCRIPTOR base table . 146
21.16 DIRECT_SUPERTABLES . 150
21.23 METHOD_SPECIFICATION_PARAMETERS . 150
4 ©  ISO/IEC 2000 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E)
21.24 METHOD_SPECIFICATIONS base table . 151
21.25 PARAMETERS base table . 152
21.33 ROUTINES base table . 152
21.34 SCHEMATA base table . 152
21.35 SQL_FEATURES base table . 153
21.36 SQL_IMPLEMENTATION_INFO base table . 153
21.38 SQL_SIZING base table . 153
21.39 SQL_SIZING_PROFILES base table. 154
21.43 TABLES base table . 154
21.44 TRANSFORMS base table . 155
21.45 TRANSLATIONS base table . 155
21.47 TRIGGER_COLUMN_USAGE base table . 155
21.49 TRIGGERS base table . 156
21.52 USER_DEFINED_TYPES base table . 157
21.56 VIEWS base table . 158
22.1 SQLSTATE . 158
22.3 SQL Multimedia and Application Package SQLSTATE Subclasses . 158
23.1 General conformance requirements . 158
Annex A SQL conformance summary . 158
Annex B Implementation-defined elements . 164
Annex C Implementation-dependent elements . 165
Annex E Incompatibilities with ISO/IEC 9075:1992 and ISO/IEC 9075-4:1996 . 166
Annex F SQL feature and package taxonomy . 167
ISO/IEC 9075-3:1999
Database Languages - SQL-Part 3:Call Level Interface . 169
3.1.1.Definitions provided in Part 3 . 169
3.3.2.1 Clause, subclause and table relationships . 169
4.4.5 Connection attributes . 170
5.1 . 170
5.3 Description of CLI item descriptor areas . 170
5.5 Implicit DESCRIBE USING clause . 171
5.11 Deferred parameter check . 171
5.13 Description of CLI item descriptor areas . 171
5.14 Other tables associated with CLI . 172
5.15 Data type correspondences . 173
6.5 BindCol . 174
6.6 BindParameter . 174
6.9 ColAttribute . 174
6.10 ColumnPrivileges . 175
6.11 Columns . 175
6.12 Connect . 175
6.14 DataSources . 176
6.15 DescribeCol . 176
6.17 EndTran . 177
6.18 Error . 178
6.19 ExecDirect . 178
6.21 Fetch . 178
6.22 FetchScroll . 179
6.23 ForeignKeys . 179
6.28 GetConnectAttr . 180
6.29 GetCursorName . 180
6.30 GetData . 180
6.32 GetDescRec . 180
6.34 GetDiagRec . 181
  ©  ISO/IEC 2000 – All rights reserved 5

---------------------- Page: 5 ----------------------
ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E)
6.36 GetFeatureInfo . 181
6.40 GetParamData . 181
6.50 Prepare . 182
6.51 PrimaryKeys . 182
6.54 SetConnectAttr . 182
6.55 SetCursorName . 182
6.56 SetDescField . 183
6.60 SpecialColumns . 183
6.62 TablePrivileges . 183
6.63 Tables . 184
A.1 C header file SQLCLI.H . 184
A.2 COBOL library item SQLCLI . 185
ISO/IEC 9075-4:1999
Database Languages - SQL-Part 4:Persistent Stored Modules . 187
3.3.2.1 Clause, Subclause, and Table relationships . 187
4.8 Cursors . 187
4.10 SQL-statements . 187
4.10.1 SQL-statements classified by function . 188
5.1 and . 188
6.2 . 188
9.18 . 189
11.2 . 189
12.2 . 189
13.1 . 190
13.6 . 190
13.7 . 190
15.1 . 191
16.1 . 191
16.3 . 191
17.2 MODULE_PRIVILEGES view . 191
17.4 MODULES view . 192
Annex A SQL Conformance Summary . 192
Annex E Incompatibilities with ISO/IEC 9075:1992 . 193
Annex F SQL Feature Taxonomy . 193
ISO/IEC 9075-5:1999
Database Languages - SQL-Part 5:Bindings . 195
4.6.1 Classes of SQL-statements . 195
4.6.4 Embeddable SQL-statement . 195
4.6.5 Preparable and immediately executable SQL-statements . 195
4.6.6 Directly executable SQL-statements . 196
5.1 and . 196
10.5 . 197
11.2 Calls to an . 197
11.3 . 197
12.0 . 197
12.1 . 198 12.2 . 198 14.3 . 199 15.1 Description of SQL descriptor areas . 199 15.6 . 199 15.8 . 200 15.13 . 200 15.14 . 200 6 ©  ISO/IEC 2000 – All rights reserved ---------------------- Page: 6 ---------------------- ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E) 16.1 . 201 16.3 . 203 16.4 . 204 16.5 . 204 16.6 . 205 16.7 . 206 16.8 . 206 16.9 . 207 19.1 . 208 20.1 SQLSTATE . 208 Annex A SQL Conformance Summary . 209 Annex E Incompatibilities with ISO/IEC 9075:1992 . 211   ©  ISO/IEC 2000 – All rights reserved 7 ---------------------- Page: 7 ---------------------- ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E) 8 ©  ISO/IEC 2000 – All rights reserved ---------------------- Page: 8 ---------------------- ISO/IEC 9075 (parts 1 to 5):1999/Cor.1:2000(E) ISO/IEC 9075-1:1999 Database Languages - SQL-Part 1:Framework 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-holdable locator remains valid until the end of the SQL-transaction in which it was generated, 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 . th Replace 9 paragraph with: A holdable locator may remain valid beyond the end of the SQL-transaction in which it is generated. A holdable locator becomes invalid whenever a identifying that locator is executed or the SQL-transaction in which it is generated or any subsequent SQL-transaction is rolled back. All locators ...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.