ISO/IEC 9075-5:1999/Amd 1:2001/Cor 1:2003
(Corrigendum)Information technology — Database languages — SQL — Part 5: Host Language Bindings (SQL/Bindings) — Amendment 1: On-Line Analytical Processing (SQL/OLAP) — Technical Corrigendum 1
Information technology — Database languages — SQL — Part 5: Host Language Bindings (SQL/Bindings) — Amendment 1: On-Line Analytical Processing (SQL/OLAP) — Technical Corrigendum 1
Technologies de l'information — Langages de base de données — SQL — Partie 5: Liants de langage d'hôte (SQL/Liants) — Amendement 1: Traitement analytique en ligne (SQL/OLAP) — Rectificatif technique 1
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-5:1999/Amd.1:2001
TECHNICAL CORRIGENDUM 1
Published 2003-06-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Database languages — SQL —
Part 5:
Host Language Bindings (SQL/Bindings)
AMENDMENT 1: On-Line Analytical Processing (SQL/OLAP)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données — SQL —
Partie 5: Liants de langage d'hôte (SQL/Liants)
AMENDEMENT 1: Traitement analytique en ligne (SQL/OLAP)
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to ISO/IEC 9075-5:1999/Amd.1:2001 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-5:1999/Amd.1:2001/Cor.1:2003(E)
© ISO/IEC 2003 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9075-5:1999/Amd.1:2001/Cor.1:2003(E)
Contents
Page
Introduction . . . . . . . . 3
3.3.2.1 Clause, Subclause, and Table relationships . . . . . 3
4.1.1 Operations invo lving numbers . . . . . 3
5.1 an d . . . . . 4
6.1 . . . . . 4
6.2 . . . . . . 5
6.4 . . . . . 7
7.0 . . . . . . 7
7.5 . . . . . . 8
7.6 . . . . . 8
8.1 . . . . . 8
13 In formation Schema . . . . . 10
Annex B Implem entation-de fined eleme nts . . . . . 10
Annex F Incompatibilities with ISO/IEC 9075:1992 . . . . . 10
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9075-5:1999/Amd.1:2001/Cor.1:2003(E)
Information technology — Database languages — SQL —
Part 5:
Host Language Bindings (SQL/Bindings)
AMENDMENT 1
TECHNICAL CORRIGENDUM 1
Introduction
1. Rationale: Add description of new Annex.
Insert the follow ing point:
21) Annex F, ‘‘Incomp atibilities with ISO /IEC 907 5:1992’’, is an informative A nnex. It lists
incompatibilities with the previous version of ISO/IEC 9075.
3.3.2.1 Clause, Subclause, and Table relationships
1. Rationale: Add relationship for new Annex.
Insert the following row into Table 1 "Clause, Subclause, and Table relationships":
Clause, Subclause, or Table in this part Corresponding Clause, Subclause, or Part containing correspondence
of ISO/IEC 9075 Table from another part
Annex F, ‘‘Incompatibilities with ISO/IEC (none) (none)
9075:19 92’’
4.1.1 Operations involving numbers
1. Rationale: Editorial.
th st
Replace the 7 bullet of the 1 paragraph with:
— is a function of four arguments, returning an integer between 0 (zero) and the
value of the final argument plus 1 (one), by assigning the first argument to an equi-width partitioning of
the range of numbers between the second and third arguments. Values outside the range between the
second and third arguments are assigned to either 0 (zero) or the value of the final argument plus 1
(one).
NOTE 2 – The semantics of are illustrated in Figure 1, ‘‘Illustration of
WIDTH_BUCKET Semantics’’.
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 3 ----------------------
ISO/IEC 9075-5:1999/Amd.1:2001/Cor.1:2003(E)
5.1 and
1. Rationale: Correct the BNF of and .
Replace the productions for and with:
::=
!! All alternatives from ISO/IEC 9075-2
| !! All alternatives from ISO/IEC 9075-5
| EXCLUDE
| FOLLOWING
| NULLS
| OTHERS
| PRECEDING
| TIES
| UNBOUNDED
::=
!! All alternatives from ISO/IEC 9075-2
| !! All alternatives from ISO/IEC 9075-5
| CEIL | CEILING | CORR | COVAR_POP | COVAR_SAMP | CUME_DIST
| DENSE_RANK
| EXP
| FILTER | FLOOR
| LN
| OVER
| PARTITION | PERCENTILE_CONT | PERCENTILE_DISC | PERCENT_RANK | POWER
| RANGE | RANK | REGR_AVGX | REGR_AVGY | REGR_COUNT | REGR_INTERCEPT
| REGR_R2 | REGR_SLOPE | REGR_SXX | REGR_SXY | REGR_SYY | ROW_NUMBER
| SQRT | STDDEV_POP | STDDEV_SAMP
| VAR_POP | VAR_SAMP
| WIDTH_BUCKET | WINDOW | WITHIN
6.1
1. Rationale: The definition of aggregated argument must overlay the definition in ISO/IEC 9075-2:1999
introduced by a correction elsewhere in this TC.
Replace Syntax Rule 5) with:
5) Replace SR 3.1) | A VE simply contained in a SFE is
an aggregated argu ment of SFE if either SFE is not an or VE is simply
contained in a ; oth erwise, VE is a non-aggregated arg ument of SFE.
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 9075-5:1999/Amd.1:2001/Cor.1:2003(E)
6.2
1. Rationale: Clarify the declared type of
Replace Syntax Rules 1), 2) and 3) with:
1) Insert this SR The declared type of the result of is an implementation-defined
approximate numeric type.
2) Insert this SR The declared type of the result of is an implementation-
defined approximate numeric type.
3) Insert this SR The declared type of the result of is an implementation-defined
approximate numeric type.
2. Rationale: Correct the result data type of and .
Replace Syntax Rule 5) with:
5) Insert this SR If is specified, then
Case:
a) If the declared type of the simply contained NVE is exact numeric,
then the de clared type of the result is ex act numeric with implem entation-de fined precisio n, with
the radix of NVE, and with scale 0 (zero).
b) Otherwise, the declared type of the result is approximate numeric with implementation-defined
precision.
3. Rationale: Correct the result data type of and .
Replace Syntax Rule 6) with:
6) Insert this SR If is specified, then
Case:
a) If the declared type of the simply contained NVE is exact numeric,
then the de clared type of the result is ex act numeric with implem entation-de fined precisio n, with
the radix of NVE, and with scale 0 (zero).
b) Otherwise, the declared type of the result is approximate numeric with implementation-defined
precision.
4. Rationale: Correct the result data type of and .
Replace General Rule 4) with:
4) Insert this GR If is spec ified, then let V be the value of the simply contained
NVE.
© ISO/IEC 2003 – All rights reserved 5
---------------------- Page: 5 ----------------------
ISO/IEC 9075-5:1999/Amd.1:2001/Cor.1:2003(E)
Case:
a) If V is the null value, then the result is the null value.
b) Otherwise,
Case:
i) If the most specific type of NVE is exact num eric, then the re sult is the greate st exact num eric
value with scale 0 (zero) that is less than or equal to V. If this result is not representable by the
result data typ e, then an ex ception co ndition is raised : data exception — numeric value out of
range.
ii) Otherwise, the result is the greatest whole number that is less than or equal to V. If this result is
not represe ntable by th e result data typ e, then an ex ception co ndition is raised : data exception
— numeric value out of range.
5. Rationale: Correct the result data type of and .
Replace General Rule 5) with:
5) Insert this GR If is spe cified, then let V be the value of the simply contained
NVE.
Case:
a) If V is the null value, then the result is the null value.
b) Otherwise,
Case:
i) If the most specific type of NVE is exact num eric, then the re sult is the least ex act nume ric
value with scale 0 (zero) that is greater than or equal to V. If this result is not representable by
the result data ty pe, then an exception c ondition is raise d: data exception — numeric value out
of range.
ii) Otherwise, the result is the least whole number that is greater than or equal to V. If this result is
not represe ntable by th e result data typ e, then an ex ception co ndition is raised : data exception
— numer
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.