SubCommittee Namejtc1sc32.org/doc/N2351-2400/32N2353-summ_of_voting-N2311... · Web viewIn addition, a word “item” at the end of 5th sentence is not expected, since the referent

ISO/IEC JTC 1/SC 32 N 2353Date: 2013-06-08

REPLACES: —

ISO/IEC JTC 1/SC 32

Data Management and Interchange

Secretariat: United States of America (ANSI)Administered by Farance Inc. on behalf of ANSI

DOCUMENT TYPE Summary of Voting/Table of RepliesTITLE Summary of Voting on 32N2311 ISO/IEC CD 9075-2 Information technology -

Database languages - SQL - Part 2: Foundation (SQL/Foundation) Ed 5SOURCE SC32 SecretariatPROJECT NUMBER 1.32.03.08.02.00STATUS The document did not obtain substantial support. WG3 is requested to address

the comments and revise the draft text accordingly.REFERENCESACTION ID. ACTREQUESTED ACTIONDUE DATENumber of Pages 80LANGUAGE USED EnglishDISTRIBUTION P & L Members

SC ChairWG Conveners and Secretaries

Dr. Timothy Schoechle, Secretary, ISO/IEC JTC 1/SC 32Farance Inc *, 3066 Sixth Street, Boulder, CO, United States of AmericaTelephone: +1 303-443-5490; E-mail: [email protected] from the JTC 1/SC 32 WebSite http://www.jtc1sc32.org/ *Farance Inc. administers the ISO/IEC JTC 1/SC 32 Secretariat on behalf of ANSI

http://www.jtc1sc32.org/

mailto:[email protected]

Template for comments and secretariat observations Date: Document: Germany on CD 9075-2

Project:

MB/NC1

Line number(e.g. 17)

Clause/ Subclause(e.g. 3.1)

Paragraph/ Figure/ Table/

(e.g. Table 1)

Type of comment

2

Comments Proposed change Observations of the secretariat

DE P02-No specific location

TE All Possible Problems and problems that are discovered during the editing process must be satisfactorily resolved.

Solution: None provided with comment.

DE P02-No specific location

TE SQL is missing a data type to store multi-dimensional arrays in a column, together with appropriate declarative operations on these arrays. This "Array SQL" functionality should be based on the existing stub functionality for arrays available since SQL:1998. It needs to be generic enough to accommodate both densely and sparsely populated arrays. Array storage and retrieval is essential for capturing a main component of Big Data in science and engineering, such as: 1-D timeseries; 2-D satellite imagery and confocal microscopy; 3-D x/y/t earth observation and astrophysical image timeseries as well as x/y/z geological models; 4-D x/y/z/t climate and ocean simulation output. Today this massive amount of data is maintained outside databases in ad-hoc implemented systems. By adding array support to SQL, databases will get enabled for Big Data Analytics on an information category critical to science, engineering, and society


1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)2 Type of comment: ge = general te = technical ed = editorial

page 1 of 90ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03


Project:

MB/NC1




(e.g. Table 1)

Type of comment

2


at large. DE P02-2.1

ISO and IEC standards

ed For ISO/ 9075 Part 1 and 3 is the 2011 edition referenced. It should be the current edition.

Solution: Fix the reference

DE P02-4.2.3.4 Operationinvolving large object character strings

te Currently the SIMILAR predicate is able to operate on large object character strings. The Regex like predicate is not able to do so. Enhance Regex for large object character strings


DE P02-8.6 <similar predicate>

ED In Annex D is Feature T141, “SIMILAR predicate” deprecated. It should be removed. Can we also remove Feature T581 regular expression substring function? Check also Subclauses 4.2.3.1 Regular expression syntaxes, 4.2.3.3 Other operators involving character strings, 6.12 <case expression>, 6.30 <string value function>, 8.1 <predicate> and 20.6 <prepare statement>


DE P02-Annex E Incompatibilities with

ED The name of the Annex and the references should reference SQL 2011 The list of incompatibilities is outdated

Solution: Fix the reference and remove the list.




Project:

MB/NC1




(e.g. Table 1)

Type of comment

2


ISO/IEC 9075:2008

DE P02-Bibliography

ed For ISO/IEC 9075 the 2008 and 2011 editions are referenced. It should be the current edition.

Solution: Fix the reference



Template for comments and secretariat observations Date: Document: ISO/

1 2 3 4 5 6 7

MB1

Clause/Subclause/

Annex/Figure/Table

(e.g. 3.1, Table 2)

Paragraph/

List item/Note/

(e.g. Note 2)

Type of

com-ment

2

Comment (justification for change) Proposed change Secretariat observationson each comment submitted

WG3/National Body JPN CD 9075-2 Comments — 2013-04-25

SEQ#

CmntID

SeeAlso Severit

yReference Description

Addressed By

CD SQL/FoundationP02-JPN-001 4-Minor

EditorialP02-4.2.4 Character repertoires

The wrong standard number 19075 appears in the lead text of the third paragraph.

SolutionModify the lead text of third paragraph as follows:

The following character repertoire names are specified as part of ISO/IEC 19075:

See comment.

P02-JPN-002 4-Minor Editorial

P02-4.4.3 Operations involving numbers

In the 5th list item in the first paragraph, Subclause 4.10.6,“Operations involving multisets” is referenced for <max cardinality expression>. However, the <max cardinality expression> is not mentioned in Subclause 4.10.6, because a max cardinality is a property of an array type, not of a multiset type.

SolutionModify the 5th list item in the first paragraph as follows:

— <max cardinality expression> (see Subclause 4.10.5, “Operations involving arrays”, and Subclause 4.10.6, “Operations involving multisets”) operates on an array argument and returns an integer.

See comment.


P02-4.15.2.3 Temporary

The term “temporary base table” appears in the first paragraph and does not appear anywhere else in the standard. The term

See comment.

Page 4 of 1 2023-05-17

WG3/National Body JPN CD Ballot Comments TemplateSEQ

#Cmnt

IDSeeAlso Severit


Addressed By

tables “temporary table” is the correct term, because of the definition in the lead text of Subclause 4.15.2 that a regular base table is either a regular persistent base table or a temporary table. In addition, a period is missing in the first sentence in the first paragraph.

SolutionModify first paragraph as follows:

A temporary base table is either a global temporary table, a created local temporary table, or a declared local temporary table.


P02-4.15.7 Table descriptors

The word “descriptor” is the correct word rather than “description” in the third list item of the third paragraph.

SolutionModify the third list item of the 4th paragraph as follows:

The description descriptor of each period defined for the table.

See comment.


P02-4.15.10Operations involving tables

Although the 6th paragraph describes the primary effect of a delete statement on a regular base table and derived table, the term “base table” appears in the second sentence of the paragraph. It is incorrect, because a base table may be not only a regular base table, but also a system-versioned table.

SolutionModify 6th paragraph as follows:

The primary effect of a <delete statement: positioned> on a regular base table T or a derived table T is to delete exactly one specified row from T. The primary effect of a <delete statement: searched> on a regular base table T or a derived table T is to delete zero or more rows from T.

See comment.

P02-JPN-006 3-Major Editorial

P02-4.15.10Operations involving tables

The description of the primary effect of a searched delete statement on a system-versioned table should be separated from that of a positioned delete statement just like that of a regular base table in 6th paragraph of the same subclause, because the number of rows for deletion is different between those two types of delete statement.

Solution

Page 5 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

None provided with comment.P02-JPN-007 3-Major

EditorialP02-4.23.3.2Unique constraints

The condition for satisfaction of the unique constraint without a <without overlap specification> is described in the third paragraph, which reads:

A unique constraint that does not include a <without overlap specification> on a table T is satisfied if and only if there do not exist two rows R1 and R2 of T such that R1 and R2 have the same non-null values in the unique columns.

This condition is incorrect in case of a system-versioned table, because uniqueness is required only for rows with system time as of current timestamp.

SolutionNone provided with comment.


P02-4.23.3.3Referential constraints

The semantics of referential check described in the second and third paragraph are incorrect in case of a system-versioned table, because only rows with system time as of current timestamp are involved with referential check.



P02-4.24.8 Known functional dependencies in a <table primary>

Since the symbol TQN is defined immediately after the first appearing <table or query name>, TQN indicates just that <table or query name>, but cannot indicate the second one, which is contained in <only spec>, in the third list item in the second paragraph, which reads:

If TP immediately contains a <table or query name> TQN or an <only spec> that contains a <table or query name>, then the counterparts of the BPK-sets and BUC-sets of TQN are the BPK-sets and BUC-sets, respectively, of R. If A ↦ B is a known functional dependency in the result of TQN, and AC and BC are the counterparts of A and B, respectively, then AC ↦ BC is a known functional dependency in R.



P02-4.24.9 Known functional dependencies in a <table

The term “BUCset” without hyphen appears in the second sentence.Solution

Modify the text of Subclause:

See comment.

Page 6 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

factor> Let R be the result of <table factor> TF. Let S be the result of <table primary> immediately contained in TF. The counterparts of the BPK-sets and BUC-sets of S are the BPK-sets and BUC-sets, respectively, of R. If A ↦ B is a functional dependency in S, and AC and BC are the counterparts of A and B, respectively, then AC ↦ BC is a known functional dependency in R.


P02-4.41.3 Properties of SQL-transactions

An intransitive verb “execute” appears without an object in 4th paragraph. In other than Subclause 4.41.3, the similar occurrence of “execute” appears in several location in this standard.

SolutionModify 4th paragraph.as follows:

An SQL-transaction has a transaction timestamp, a value of an implementation-defined timestamp type that is used to set the values of system-time period start and system-time period end columns of rows, if any, modified by the execution of an SQL-data change statement in this SQL-transaction. The transaction timestamp is set by an SQL-implementation before any SQL-data change statement executesis executed in that transaction and, once set, remains unchanged during that SQL-transaction.

See comment.


P02-4.41.7 Encompassing transactions

The term “isolation level” appears in the second list item of the 4th paragraph. The term “transaction isolation level” is correct.

SolutionModify the first sentence of the second list item of the 4th paragraph.as follows:

If the SQL-transaction has a transaction isolation level of READ UNCOMMITTED, then the branch of the SQL-transaction may have an a transaction isolation level of READ UNCOMMITTED, READ COMMITTED, REPEATABLE READ, or SERIALIZABLE.

See comment.


P02-4.43.4 SQL-session context management

The term “SQL-session execution context” appears at the end of the 4th paragraph. The correct term is “SQL-session context”, because this paragraph is involved with a stack of SQL-session contexts.


See comment.

Page 7 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

The <value specification>s CURRENT_USER and CURRENT_ROLE identify the user name and role name on top of the authorization stack in the top of the stack of SQL-session contexts. The <value specification> SESSION_USER is the value of the SQL-session user identifier in the latest SQL-session execution context.



The term “authorization clause of the module” in 5th paragraph should be “<module authorization clause>”, because syntax element “<module authorization clause> “is defined, but the term of “authorization clause” is not defined in anywhere in the standard.


Invocation of an <externally-invoked procedure> pushes a cell on the authorization stack. If the <externally-invoked procedure> is invoked using invoker’s rights, then the new cell is a copy of the one beneath it. If it is invoked using definer's rights, the new cell is taken from the authorization clause of the module<module authorization clause>, which supplies either a user name or a role name, the other being set to the null value.

See comment.



An incorrect term “user name” appears in several places. The correct term is “user identifier”.

SolutionReplace the term “user name” in the 3rd, 4th, 5th, and 8th paragraphs with “user identifier”.

Modify 3rd, 4th, 5th paragraph.as follows:

Each SQL-session context contains an “authorization stack”. Each cell of the authorization stack is a pair, a user identifier, and a role name. Whenever an SQL-session context is created, the base of its authorization stack is initialized with the SQL-session user identifier for the user name identifier and the null value for the role name.

The <value specification>s CURRENT_USER and CURRENT_ROLE identify the user name identifier and role

See comment.

Page 8 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

name on top of the authorization stack in the top of the stack of SQL-session contexts. The <value specification> SESSION_USER is the value of the SQL-session user identifier in the latest SQL-session execution context.

Invocation of an <externally-invoked procedure> pushes a cell on the authorization stack. If the <externally-invoked procedure> is invoked using invoker’s rights, then the new cell is a copy of the one beneath it. If it is invoked using definer's rights, the new cell is taken from the authorization clause of the module, which supplies either a user name identifier or a role name, the other being set to the null value.

Modify 8th paragraph.as follows:

The <set role statement> changes the role name on top of the authorization stack in the latest SQL-session context, but does not change the user name identifier.


P02-5.2<token> and <separator>

The reserved word “TRUNCATE” is not at the position in an alphabetical order in reserved word list in the production of <reserved word> in Format.

SolutionModify the following part of the right hand side of <reserved word> in Format.

| TRIGGER | TRUNCATE | TRIM | TRIM_ARRAY | TRUE | TRUNCATE

See comment.

P02-JPN-017 2-Minor Technical

P02-6.10<window function>

After SR1) assigns WINFUNC parameter is to a symbol OF, SR3) assigns <window function> to the symbol OF.

1) Let OF be the WINFUNC in an application of the Syntax Rules of this Subclause. The result of the application of this Subclause is QSX or SSSRX, as appropriate, which is returned as TRANSFORM.

2) An <aggregate function> simply contained in a <window function> shall not simply contain a <hypothetical set function>.

3) Let OF be the <window function>.

Page 9 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

This means that the syntax element passed through WINFUNC from invoking Subclause is overwritten in SR3) and therefore WINFUNC parameter does not have any effect.




The second occurrence of “END(i–-1)” in GR1)a)ii)3)F) contains double hyphen..

SolutionModify GR1)a)ii)3)F) as follows:

F) Let END0 be 0 (zero). For each i, 1 (one) ≤ i ≤ NT, let STARTi be (END(i–1) + 1) and let ENDi be (END(i–-1) + NQi).

See comment.



The term “row ordering” appears in GR1)b)iv)1). However, “row ordering” is the term related with <row pattern recognition clause>. The term “window ordering”is a correct term.

SolutionModify GR1)b)iv)1)A) and B) as follows:

A) If NTREAT is RESPECT NULLS, then let TX be the sequence of values that is the result of applying VE1 to each row of T that precedes the current row, ordered according to the rowwindow ordering of WDX.

B) Otherwise, let TX be the sequence of values that is the result of applying VE1 to each row of T that precedes the current row and eliminating null values, ordered according to the rowwindow ordering of WDX.

See comment.


P02-6.11<nested window function>

While the symbol VE is defined to denote the <value expression> in GR4)a), it is never referred in the following GRs. “the <value expression>” appearing in GR4)e)ii) should be VE.

SolutionModify GR4)e)ii) as follows:

ii) Otherwise, the value of NWF is the value of the <value expression>VE, evaluated in ROWM.

See comment.


P02-6.23<reference resolution>,P02-8.2

While the term “reference value” appears in Function of Subclause 6.23, GR9) of Subclause 8.2, and GR1)b)i) of Subclause 11.32, “REF value” is used in everywhere else in the standard.

Solution

See comment.

Page 10 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

<comparison predicate>,P02-11.32<view definition>

Modify Function of Subclause 6.23 as follows:

Obtain the value referenced by a referenceREF value..

Modify GR9) of Subclause 8.2 as follows:

9) The result of comparing two referenceREF values X and Y is determined by the comparison of their octets with the same ordinal position. Let Lx be the length in octets of X and let Ly be the length in octets of Y. Let Xi and Yi, 1 (one) ≤ i ≤ Lx, be the values of the i-th octets of X and Y, respectively. X is equal to Y if and only if Lx = Ly and, for all i, Xi = Yi.

Modify GR1)b)i) of Subclause 11.32 as follows:

i) If RMSV has a derived representation, then let SL be the <select list> simply contained in QS, and let TE be the <table expression> simply contained in QS. Let IDV be an implementationdependent <value expression> that computes the referenceREF value that references a row of V. Let OQE be the <query expression>SELECT IDV, SL TE


P02-6.28<numeric value function>

CR5) mentions just a declared type of NATIONAL CHARACTER LARGE OBJECT as a national character type. However, NATIONAL CHARCTER and NATIONAL CHARACTER VARYING type is also national character type.

SolutionModify CR5) as follows:

5) Without Feature F421, “National character”, conforming SQL language shall not contain a <length expression> that simply contains a <string value expression> that has a declared type of NATIONAL CHARCTER and NATIONAL CHARACTER VARYING, or NATIONAL CHARACTER LARGE OBJECT.

See comment.


P02-6.29<string value expression>

Wording “the most specific type at least one of S1 and S2” in GR2)b)ii)3)A) is incomplete as a phrase.

Solution

See comment.

Page 11 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Modify the lead text of GR2)b)ii)3)A) as follows:

A) If the most specific type of at least one of S1 and S2 is a character large object type, then let LOL be the implementation-defined maximum length of large object character strings.


P02-6.30<string value function>

The last sentence of GR9)b)v)1)C), as quoted below, does not make sense.

C) Otherwise, let MV be the OCC-th match vector in LOMV. The General Rules of Subclause 9.19, “XQuery regular expression replacement”, are applied with MV as MATCH, STR as STRING, PAT as PATTERN, REP as REPLACEMENT, and FL as FLAG; let the character string be the RESULT returned from the application of those General Rules.

It is reasonable that the GR9)b)v)1) specifies the result of <regex transliteration>, like GR9)b)v)2).

SolutionModify GR9)b)v)1)C) as follows:

C) Otherwise, let MV be the OCC-th match vector in LOMV. The General Rules of Subclause 9.19, “XQuery regular expression replacement”, are applied with MV as MATCH, STR as STRING, PAT as PATTERN, REP as REPLACEMENT, and FL as FLAG; let the character string be the result of <regex transliteration> is the RESULT returned from the application of those General Rules.

See comment.


P02-6.30<string value function>,P02-Annex ASQL Conformance Summary

Although CR11) restricts the declared type of a <character value expression>, CR of Subclause 6.30 “<string vale function>” should restrict that of <string vale function>.

SolutionModify CR11) of Subclause 6.30 as follows:

11) Without Feature F421, “National character”, conforming SQL language shall not contain a <character value expressionfunction> that has a declared type of NATIONAL CHARACTER, NATIONAL CHARACTER VARYING, or NATIONAL CHARACTER LARGE OBJECT.

See comment.

Page 12 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Modify 75)f)i) of Annex A as follows:

i) Without Feature F421, “National character”, conforming SQL language shall not contain a <character value expressionfunction> that has a declared type of NATIONAL CHARACTER, NATIONAL CHARACTER VARYING, or NATIONAL CHARACTER LARGE OBJECT.


P02-7.10<joined table>

Under SR9)e)ii), subrule2) is that for RTA and subrule3) is that for RTB. However, the symbol RTA appears in SR9)e)ii)3)B), which reads:

B) Otherwise, let RVAi be some range variable that is not equivalent to any range variable in the outermost <query specification> containing the <joined table>, nor to any other range variable created by these rules. RVAi is effectively associated with the field of RTA whose name is CJCNi.

RTB is correct instead of RTA in this subrule.Solution

Modify SR9)e)ii)3)B) as follows:

B) Otherwise, let RVAi be some range variable that is not equivalent to any range variable in the outermost <query specification> containing the <joined table>, nor to any other range variable created by these rules. RVAi is effectively associated with the field of RTA RTB whose name is CJCNi.

See comment.


P02-7.10<joined table>

The character “≤” is missing in the last line of SR9)e)iii).Solution

Modify SR9)e)iii) as follows:

iii) Let SLCC be a <select list> of <derived column>s of the formCOALESCE ( RVAi.CJCNi, RVBi.CJCNi ) AS CJCNifor every i, 1 (one) ≤ i ≤ N, in ascending order.

See comment.

P02-JPN-028 1-Major Technica

P02- 7.12 <group by

Although it is not allowed to specify a value expression as a grouping element, it is necessary in some cases. For example,

Page 13 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

l clause> when grouping by the month field of a date type value, it is not necessary to describe complex nested query if an extract expression is able to specified as the grouping element such as:

GROUP BY EXTRACT(MONTH FROM date_value)To refer the result column of grouping in having clause and in select list, the declaration of a name for that result column is necessary. The extension of <group column reference> as shown below is reasonable.

<grouping column reference> ::=<value expression> [ <collate clause> ] [ <as clause> ]



P02-7.14<window clause>

Undefined symbol EC1 and EC2 appears in GR5)b)iii)3).Solution

Modify GR5)b)iii)3) as follows:

3) The distance between two window ordering groups WOG1 and WOG2 is number of window ordering groups between EC1 WOG1 and EC2 WOG2, inclusive, minus 1 (one).

See comment.


P02-7.15 <query specification>

In an application of Subclause 6.10,"<window function>", a grouped, windowed query GWQ is specified as WINFUNC parameter in SR13)a), which reads:

a) If GWQ contains an <in-line window specification>, then the Syntax Rules of Subclause 6.10, “<window function>”, are applied with GWQ as WINFUNC; let GWQ1 be the TRANSFORM returned from the application of those Syntax Rules; otherwise, let GWQ1 be GWQ.

However, Subclause 6.10 requires WINFUNC parameter to be a window function.



P02-7.15 <query specification>

The last sentence of SR13)b) is redundant, because the application of SR of the Subclause is fully described in the part before that sentence in SR13)b). The subject and the complement are reversed in the sentence.

SolutionModify SR13)b) as follows:

See comment.

Page 14 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

b) If the <select list> of GWQ1 immediately contains <asterisk> or simply contains <qualified asterisk>, then Syntax Rules of this Subclause are applied with GWQ1 as TBLEXP; let GWQ2 be the TBLEXP2 returned from the application of those Syntax Rules; otherwise, let GWQ2 be GWQ1. Apply the syntactic transformations specified in Subclause 7.15, “<query specification>”.


P02- 7.16 <query expression>

The wording “the i-th columns” in SR19)c) should be a singular form

SolutionModify SR19)c) as follows:

c) If the SQL-implementation supports Feature T101, “Enhanced nullability determination” and the i-th columns of at least one of T1 and T2 is known not nullable, then the i-th column of TR is known not nullable; otherwise, the i-th column of TR is possibly nullable.

See comment.



SR21)b)iv)2) specifies the data type and nullability of the result column of an anchor expression which is not recursively referred:

2) If the i-th column of TR is not recursively referred to, then the Syntax Rules of Subclause 9.5, “Result of data type combinations”, are applied with the set comprising the declared type of the i-th column of T1 and the declared type of the i-th column of T2 as DTSET; let the declared type of the i-th column of TR be the RESTYPE returned from the application of those Syntax Rules. If the i-th columns of at least one of T1 and T2 are known not nullable, then the i-th column of TR is known not nullable; otherwise, the i-th column of TR is possibly nullable.

This rule does not work in case of the following with list element.

WT(WC1, WC2) AS(SELECT C1,0 FROM T1

UNION ALL SELECT C1, WC1 FROM WT, T1 WHERE WT.WC1=T1.C2)

Page 15 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Although the column WC2 of WT is not recursively referred, the corresponding column of the second operand of UNION ALL is untyped and therefore Subclause 9.5 cannot be applied.




It is necessary that GR7)d) defines the cardinality of the result table. However, the description at the end of GR7)d)ii) defines FFRC value as the cardinality of the result table.

SolutionModify GR7)d)ii) as follows:

ii) Otherwise, rows other than the first FFRC rows in order as specified by General Rule 6) of this Subclause are removed from T and FFRC is the cardinality of T is FFRC.

See comment.


P02- 7.16 <query expression>,P02- Annex A SQL Conformance Summary

CR19) and 20) are inconsistent with CR12), 13), 14), and 16). CR12) and CR16) describe “in subquery” feature as follows:

a <query expression> contained in another <query expression> shall not immediately contain …..

CR13) and CR14) describe “nested” feature as follows:

a <query primary> shall not immediately contain…..

On the other hand, in CR19) and 20) the description for “in subquery” feature and that for “nested” feature is swapped

12) Without Feature F851, “<order by clause>in subqueries”, in conforming SQL language, a <query expression> contained in another <query expression> shall not immediately contain an <order by clause>.

13) Without Feature F855, “Nested <order by clause>in <query expression>”, in conforming SQL language, a <query primary> shall not immediately contain an <order by clause>.

14) Without Feature F856, “Nested <fetch first clause>in <query expression>”, in conforming SQL language, a <query primary> shall not immediately contain a <fetch

See comment.

Page 16 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

first clause>.15) …..16) Without Feature F858, “<fetch first clause>in subqueries”, in conforming SQL language, a <query expression> contained in another <query expression> shall not immediately contain a <fetch first clause>.

17) …..18) …..19) Without Feature F862, “<result offset clause>in subqueries”, in conforming SQL language, a <query primary> shall not immediately contain a <result offset clause>.

20) Without Feature F863, “Nested <result offset clause>in <query expression>”, in conforming SQL language, a <query expression> contained in another <query expression> shall not immediately contain a <result offset clause>.

SolutionModify CR19) and 20) of Subclause 7.16 as follows:

19) Without Feature F862, “<result offset clause>in subqueries”, in conforming SQL language, a <query primary> shall not immediately contain a <result offset clause> a <query expression> contained in another <query expression> shall not immediately contain a <result offset clause>.

20) Without Feature F863, “Nested <result offset clause>in <query expression>”, in conforming SQL language, a <query expression> contained in another <query expression> shall not immediately contain a <result offset clause> a <query primary> shall not immediately contain a <result offset clause>.

Modify 132)a)i) of Annex A as follows:

i) Without Feature F862, “<result offset clause>in subqueries”, in conforming SQL language, a <query primary> shall not immediately contain a <result offset clause> a <query expression> contained in

Page 17 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

another <query expression> shall not immediately contain a <result offset clause>.


i) Without Feature F863, “Nested <result offset clause>in <query expression>”, in conforming SQL language, a <query expression> contained in another <query expression> shall not immediately contain a <result offset clause> a <query primary> shall not immediately contain a <result offset clause>.


P02- 7.16 <query expression>,P02- Annex A SQL Conformance Summary

A phrase “in conforming SQL language” is missing in CR22) and CR23)

SolutionModify CR22) and 23) of Subclause 7.16 as follows:

22) Without Feature F866, “FETCH FIRST clause: PERCENT option”, in conforming SQL language, <fetch first clause> shall not contain <fetch first percentage>.

23) Without Feature F867, “FETCH FIRST clause: WITH TIES option”, in conforming SQL language,<fetch first clause> shall not contain WITH TIES.


i) Without Feature F866, “FETCH FIRST clause: PERCENT option”, in conforming SQL language, <fetch first clause> shall not contain <fetch first percentage>.


i) Without Feature F867, “FETCH FIRST clause: WITH TIES option”, in conforming SQL language,<fetch first clause> shall not contain WITH TIES.

See comment.

P02-JPN-037 1-Major Technical


The standard should provide query functionality that efficiently treats graph data structure.


P02-JPN-038 1-Major P02-8.5 <like A substring specifier is an arbitrary character specifier, arbitrary Page 18 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Technical

predicate> string specifier, or any sequence of single character specifiers according to GR3)c), which reads:

c) The string PCV is a sequence of the minimum number of substring specifiers such that each portion of PCV is part of exactly one substring specifier. A substring specifier is an arbitrary character specifier, arbitrary string specifier, or any sequence of single character specifiers.

For example, suppose ‘9075-_ SQL/%’ is a character pattern. The sequence of the minimum number of substring specifiers is ‘9075-‘, ‘_’, ‘ SQL/’, ‘%’. In this substring specifiers, ‘_’ is an arbitrary character specifier, ‘%’ is an arbitrary string specifier, and ‘9075-‘ and ‘ SQL/’ are sequences of single character specifiers.GR3)d)ii) provides the condition that like predicate is true when the character string length of the operand, which reads:

ii) The <predicate>MC LIKE PCis True if there exists a partitioning of MCV into substrings such that:

1) A substring of MCV is a sequence of 0 (zero) or more contiguous characters of MCV and each character of MCV is part of exactly one substring.

2) If the i-th substring specifier of PCV is an arbitrary character specifier, then the i-th substring of MCV is any single character.

3) If the i-th substring specifier of PCV is an arbitrary string specifier, then the i-th substring of MCV is any sequence of 0 (zero) or more characters.

4) If the i-th substring specifier of PCV is a single character specifier, then the i-th substring of MCV contains exactly 1 (one) character that is equal to the character represented by the single character specifier according to the collation of the <like predicate>.

5) The number of substrings of MCV is equal to the number of substring specifiers of PCV.

Page 19 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Subrule 2) and 3) provide the condition for an arbitrary character specifier in the pattern and that for an arbitrary string specifier in the pattern. Although subrule 4) must provide the condition for a sequence of single character specifiers according to classification of a substring specifier defined in GR3)c), it actually provides the condition for a single character specifier, not a sequence of them. In addition, the substring partitioning of the pattern PCV into single characters cannot make the minimum number of substring specifiers and makes maximum number of them. This means violation of GR3)c).

Incidentally, the corresponding rule to GR3)d)ii)4) in SQL:1999 is as follows:

4) If the i-th substring specifier of PCV is neither an arbitrary character specifier nor an arbitrary string specifier, then the i-th substring of MCV is equal to that substring specifier according to the collating sequence of the <like predicate>, without the appending of <space> characters to MCV, and has the same length as that substring specifier.



P02-8.7<regex like predicate>

Undefined symbols STR, SP, and CKU appear in GR1)b). STR, SP, and CKU are assigned to parameters STRING, POSITION, UNITS of Subclause 9.18, “XQuery regular expression matching”, respectively. In GR1)b), it is necessary that STRING, POSITION, UNITS are CVE, 1, CHARACTERS, respectively.

SolutionModify GR1)b) as follows:

b) The General Rules of Subclause 9.18, “XQuery regular expression matching”, are applied with STRCVE as STRING, PAT as PATTERN, SP1 as POSITION, CLUCHARACTERS as UNITS, and FL as FLAG; let LOMV be the LIST returned from the application of those General Rules.

See comment.


P02-8.17 <submultiset predicate>

GR3)c)ii) states that for all i, j, CEi=MEj. This statement leads to the conclusion that all CEi and MEj are the same value, because for all combination of i and j, CEi=MEj. It does not meet the intention of the feature.

Page 20 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By



P02-9.3Passing a value from a host language to the SQL-server,P02-9.4 Passing a value from the SQL-server to a host language,P02-9.16 Execution of array-returning functions,P02-10.4 <routine invocation>,P02-11.60 <SQL-invoked routine>,P02-11.61 <alter routine statement>

Two kinds of notation are used for SQL data type column and host data type column in operative data type correspondences table. While in some Subclauses notation enclosed by quotation mark, such as “SQL data type” column and “host data type column” are used, in other Subclauses the notation without quotation, such as SQL data type column and host data type column are used. One kind of notation should be used.



P02-9.3Passing a value from a host language to the SQL-server

In GR4)a), symbol “LANG” is not italic form. In addition, “Ada”, “Fortran”, “Pascal”, and “PL/I” should be “ADA”, “FORTRAN”, “PASCAL”, and “PLI”, just like GR3).

SolutionModify GR4)a) as follows:

a) If DT contains <locator indication>, thenCase:

i) If LANG LANG is AdaADA, then Interfaces.SQL.INT.ii) If LANG LANG is C, then unsigned long.iii) If LANG LANG is COBOL, then PIC S9(9) USAGE IS

BINARY.

See comment.

Page 21 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

iv) If LANG LANG is FortranFORTRAN, then INTEGER.v) If LANG LANG is M, then character.vi) If LANG LANG is PascalPASCAL, then INTEGER.vii) If LANG LANG is PL/I, then FIXED BINARY(31).


P02-9.4Passing a value from the SQL-server to a host language

In GR3)a), symbol “LANG” is not in italic form. In addition, “Ada”, “Fortran”, “Pascal”, and “PL/I” should be . “ADA”, “FORTRAN”, “PASCAL”, and “PLI”, just like GR2).


a) If DT contains <locator indication>, thenCase:

i) If LANG LANG is AdaADA, then Interfaces.SQL.INT.ii) If LANG LANG is C, then unsigned long.iii) If LANG LANG is COBOL, then PIC S9(9) USAGE IS

BINARY.iv) If LANG LANG is FortranFORTRAN, then INTEGER.v) If LANG LANG is M, then character.vi) If LANG LANG is PascalPASCAL, then INTEGER.vii) If LANG LANG is PL/I, then FIXED BINARY(31).

See comment.


P02-9.4Passing a value from the SQL-server to a host language

The unexpected “respectively” appears in GR5)a).Solution

Modify GR5)a) as follows:

a) If DT contains <locator indication>, then let the value of PI be the binary large object locator value, the character large object locator value, the array locator value, the multiset locator value, or the userdefined type locator value, respectively, that uniquely identifies SV.

See comment.


P02-9.5Result of data type combinations

A word is missing between “the” and “in” in SR3)h)i).Solution

Modify SR3)h)i) as follows:

i) If the field in the same ordinal position as FDi in every row type in DTS have the same name F, then the <field name> in FDi is F.

See comment.


P02-9.16 Execution of

A word “table” in “operative data type correspondences table” in GR7)a) is not in italic form.

See comment.

Page 22 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

array-returning functions


a) Depending on whether the language of P specifies ADA, C, COBOL, FORTRAN, M, PASCAL, or PLI, let the operative data type correspondences tabletable be Table 16, “Data type correspondences for Ada”, Table 17, “Data type correspondences for C”, Table 18, “Data type correspondences for COBOL”, Table 19, “Data type correspondences for Fortran”, Table 20, “Data type correspondences for M”, Table 21, “Data type correspondences for Pascal”, or Table 22, “Data type correspondences for PL/I”, respectively. Refer to the two columns of the operative data type correspondences table as the “SQL data type” column and the “host data type” column.


P02-9.16 Execution of array-returning functions

Throughout General Rules, the notation form of open call is different from fetch call and close call. While the notation of open call is double quotation-enclosed form “open call”, those of other calls are italic form fetch call, close call..

SolutionModify the lead text of GR9) as follows:

9) 13 If the call type data item has a value of –1 (indicating “open call” open call), then:

See comment.


P02-9.18XQuery regular expression matching

A wrong spelling “he” appears in NOTE339 instead of “the”.Solution

Modify NOTE339 as follows:

NOTE 339 — For example, if S is 'a', then there are four position/lengths, namely (1,0), denoting the zero-length substring at the beginning of S; (2,0), denoting the zero-length substring at the end of S; (1,1), denoting the whole string S; and (0,0), denoting no substring of S.

See comment.


P02-9.30Determination of view component privileges

The wording “<from clause> VCi” in the lead text of GR5)b)i) is wrong, because VCi is supposed to be a <query specification> in the lead text of GR5)b).

Solution

See comment.

Page 23 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Modify the lead text of GR5)b)i) as follows:

i) If the <from clause> of VCi contains exactly one <table reference> TR, then.


P02-10.4 <routine invocation>

The lead text of SR9) does not make sense, because symbol R denotes an SQL-invoked routine and a syntax element contained in <call statement> is <routine invocation>.

SolutionModify the lead text of SR9) as follows:

9) If RI is immediately contained in a <call statement>, then:

See comment.



The wording “shall contain” in SR9)a)ii) should be “contains”, because SR9)a)ii) describes a condition.

SolutionModify SR9)a)ii) as follows:

ii) If the <SQL argument list> does not contain any <SQL argument> that is a <named argument specification>, then for each k, NA < k ≤ SIRNA, the routine descriptor of SIR shall contains an indication that the k-th SQL parameter has a default value.

See comment.



Undefined symbol Pi appears in SR9)g)i)2)A).Solution

Modify the lead text of SR9)g) as follows:

g) Let SRNP be the number of SQL parameters of SR. Let Pi, 1 (one) ≤ i ≤ SRNP, be the i-th SQL parameter of SR.

See comment.



In SR9)g)iii)3), an argument of a routine invocation is specified as a target of store assignment and an input SQL parameter of a routine is specified as a value of the store assignment. However, a target must be an input parameter and a value must be an argument on a routine invocation.

SolutionModify the lead text of SR9)g)iii)3) as follows:

3) 04 If XAi is an <SQL parameter reference>, a <column reference>, or a <target array element specification>, then the Syntax Rules of Subclause 9.2, “Store assignment”, are

See comment.

Page 24 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

applied with XAi Pi as TARGET and Pi XAi as VALUE.P02-JPN-054 4-Minor

EditorialP02-10.4 <routine invocation>

The lead text of SR10) does not make sense, because symbol R denotes an SQL-invoked routine and a syntax element contained in <call statement> is <routine invocation>.


10) If RI is not immediately contained in a <call statement>, then:

See comment.



In SR10)b)ix), an argument of a routine invocation is specified as a target of store assignment and an input SQL parameter of a routine is specified as a value of the store assignment. However, a target must be an input parameter and a value must be an argument on a routine invocation.

SolutionModify the lead text of SR10)b)ix) as follows:

ix) For each Pi, the Syntax Rules of Subclause 9.2, “Store assignment”, are applied with Ai Pi as TARGET and PiAi as VALUE.

See comment.



SR12)a) does not make sense, because symbol R denotes an SQL-invoked routine and a syntax element contained in <call statement> is <routine invocation>.

SolutionModify SR12)a) as follows:

a) If RI is not immediately contained in a <call statement> and <SQL argument list> does not immediately contain at least one <SQL argument>, then let the static SQL argument list of RI be an empty list of SQL arguments.

See comment.



Even though a diagnostics area is pushed in a diagnostics area stack in GR5)f), it is not popped anywhere.



P02-10.9 <aggregate function>

Although some kind of data analysis needs a feature for iteration of product, the current standard does not provide a set function for it. For example, in some case, to estimate likelihood for series of instance of random variable , it is necessary to

Page 25 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

calculate the following products, where is probability that occurs:

That calculation can be made using a recursive query or combining an exponential, summation and logarithm

. However, SQL code for these methods is more complex and needs redundant calculation.



P02-11.2 <drop schema statement>

In NOTE 381, a redundant “by” appears. Solution

Modify NOTE 381 as follows:

NOTE 381 — If CASCADE is specified, then such objects will be dropped by implicitly by the <revoke statement> and/or explicitly by the SQL-schema manipulation statements specified in the General Rules of this Subclause.

See comment.


P02-11.4 <column definition>

GR4) enumerates items included in a column descriptor. However, GR4)f)iv) describes how to derive a sequence generator descriptor but does not describe such an item.

SolutionModify GR4)f)iv) as follows:

4) A column descriptor is created that describes the column being defined. The column descriptor includes:a) …..…..f) If <identity column specification> is specified, then:

i) An indication that the column is an identity column.ii) If ALWAYS is specified, then an indication that values are always generated.

iii) If BY DEFAULT is specified, then an indication that values are generated by default.

iv) The General Rules of Subclause 9.26, “Creation of a sequence generator”, are applied with SGO as OPTIONS and ICT as DATA TYPE; let the descriptor

See comment.

Page 26 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

of the sequence generator SG be the SEQGENDESC returned from the application of those General Rules.The descriptor of the sequence generator SG returned as SEQGENDESC from the application of the General Rules of Subclause 9.26, “Creation of a sequence generator” with SGO as OPTIONS and ICT as DATA TYPE.


P02-11.26<drop table constraint definition>

The second sentence of SR10)b) is a little bit incorrect.

TC shall not cause the nullability characteristic of the ATPN start column of T or the ATPN end column of T to change from known not nullable to possibly nullable.

TC makes some column not nullable but does not make any column possibly nullable. The dropping of TC makes it possibly nullable.


b) Let ATPN be the <application time period name> included in ATPD. The dropping of TC shall not cause the nullability characteristic of the ATPN start column of T or the ATPN end column of T to change from known not nullable to possibly nullable..

See comment.


P02-11.26<drop table constraint definition>

In NOTE 412, the wording “specified in the General Rules of this Subclause” is better than “specified in this Subclause”, just like that in NOTE 409, which reads:

NOTE 409 — If CASCADE is specified, then any such dependent object will be dropped by the execution of the <revoke statement> and/or explicitly by the SQL-schema manipulation statements specified in the General Rules of this Subclause.

SolutionModify NOTE 412 as follows:

NOTE 412 — If CASCADE is specified, then any such dependent object will be dropped implicitly by the <revoke

See comment.

Page 27 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

statement> and/or explicitly by the SQL-schema manipulation statements specified in the General Rules of this Subclause.


P02-11.27 <add table period definition>

SR4)a) is a little bit incorrect, since what a table descriptor includes is not a period but a period descriptor.

SolutionModify SR4)a) as follows:

a) The table descriptor of T shall not include a system-time period descriptor.

See comment.


P02-11.32<view definition>

The term “update column privilege” in NOTE 429 should be a capital letter form “UPDATE column privilege”, similar to “UPDATE privilege” which appears in many places in the standard.


NOTE 429 — This ensures that the updatable columns of SUPERT can be determined when the view is created and will not be subject to change as a result of adding the subview. It also ensures that updateUPDATE column privileges on SUPERT can be established solely by examining the original <query expression> of SUPERT, and need not change as the result of adding a subview. In more detail, the rule says that if a column of a referenceable view RV is a column reference to a column of the basis table of RV, then in every subview SUBRV, that column must be a column reference to the corresponding column in the basis table of SUBRV..

See comment.


P02-11.34<domain definition>

The wording “domain constraint included in the domain descriptor” in GR4) is a little bit incorrect, because what a domain descriptor includes is not a domain constraint but a domain constraint descriptor according to GR3), which reads:

3) A domain descriptor is created that describes the domain being created. The domain descriptor contains the name of the domain, the data type descriptor of the declared type, the value of the <default clause> if the <domain definition> immediately contains <default clause>, and a domain constraint descriptor for every immediately contained <domain constraint>..

See comment.

Page 28 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Solution

Modify GR4) as follows:

4) A privilege descriptor is created that defines the USAGE privilege on this domain to the <authorization identifier> A of the schema or SQL-client module in which the <domain definition> appears. This privilege is grantable if and only if the applicable privileges for A include a grantable REFERENCES privilege for each <column reference> contained in the <search condition> of every domain constraint descriptor included in the domain descriptor and a grantable USAGE privilege for each <domain name>, <collation name>, <character set name>, and <transliteration name> contained in the <search condition> of every domain constraint descriptor included in the domain descriptor. The grantor of the privilege descriptor is set to the special grantor value “_SYSTEM”.


P02-11.50<drop trigger statement>

The term “schema name” in SR2) should be BNF form “<schema name>”.

SolutionModify SR2) as follows:

2) The schema identified by the explicit or implicit <schema name> of TRN

See comment.


P02-11.51 <user-defined type definition>

The term “locator indication” in GR1)h)viii) should be BNF form “<“locator indication >”, since it is described as contained in <returns clause>. .

SolutionModify GR1)h)viii) as follows:

viii) The <locator indication> contained in the <returns clause> included in the DCMS, if any.

See comment.


P02-11.56<add original method specification>

The term “SQL descriptor” in GR1)f) is incorrect..Solution

Modify GR1)f) as follows:

f) For every SQL descriptorparameter declaration in NPL, a

See comment.

Page 29 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

locator indication (if specified).P02-JPN-069 4-Minor

EditorialP02-11.57<add overriding method specification>

A subscript “j” appears in SR9)c) with no mention about its range. It is right to use subscript “i” instead of “j”.

SolutionModify SR9)c) as follows:

c) For i varying from 2 to N, the Syntax Rules of Subclause 9.20, “Data type identity”, are applied with the declared type of SQL parameter PCOMSi of UPCOMS as TYPE1 and the declared type of SQL parameter POVMSji–1 of MPDL as TYPE2.

See comment.


P02-11.60 <SQL-invoked routine>

Although SR6)o) allows that a <returns data type> or <result cast from type> of a multiset-returning external function is a distinct type whose source type is a collection type, that data type shall be a multiset type, since a collection type includes an array type.

SolutionModify SR6)o)i) and ii) as follows:

i) A <result cast from type> is specified that simply contains a <multiset type> or a <path-resolved user-defined type name> whose source type is a collection multiset type and does not contain a <locator indication>.

ii) A <result cast from type> is not specified and <returns data type> simply contains a <multiset type> or a <path-resolved user-defined type name> whose source type is a collection multiset type and does not contain a <locator indication>.

See comment.



While symbol PDi is defined on the top of SR12), it is defined again in SR12)e)i). PDi defined in SR12)e)i) should be replaced with a different symbol to avoid any confusion.




A undefined symbol “T” appears in SR20)d)iv)1)B)I)2)a). Guessing from the description of SR20)d)iv)1)B)I)1)a), symbol “Ti” is correct one.

SolutionModify SR20)d)iv)1)B)I)2)a) as follows:

See comment.

Page 30 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

a) The Syntax Rules of Subclause 9.23, “Determination of a to-sql function”, are applied with the data type identified by Ti as TYPE and the <group name> contained in the <group specification> that contains T as GROUP. There shall be an applicable to-sql function TSFi. TSFi is called the to-sql function associated with i-th SQL parameter.


P02-11.61<alter routine statement>

In SR9)b), the quotation “host data type column” is closed at a wrong position. “host data type” column is correct.


b) Depending on whether the <language clause> specifies ADA, C, COBOL, FORTRAN, M, PASCAL, or PLI, let the operative data type correspondences table be Table 16, “Data type correspondences for Ada”, Table 17, “Data type correspondences for C”, Table 18, “Data type correspondences for COBOL”, Table 19, “Data type correspondences for Fortran”, Table 20, “Data type correspondences for M”, Table 21, “Data type correspondences for Pascal”, or Table 22, “Data type correspondences for PL/I”, respectively. Refer to the two columns of the operative data type correspondences table as the “SQL data type” column and the “host data type” column”.

See comment.



The feature to convert a table value to another table value is desirable. However, it is prohibited that a table function has a table type parameter.



P02-12.7<revoke statement>

The term “SQL routine body” appears in GR29)e), g), k), and l). It should be BNF form “< SQL routine body >”.

SolutionModify SR29)e) as follows:

e) SELECT privilege on at least one column of each table identified by a <table reference> contained in a <value expression> simply contained in an <update source> or an

See comment.

Page 31 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

<assigned row> contained in the <SQL routine body> of RD.

Modify SR29)g) as follows:

g) SELECT privilege on at least one column identified by a <column reference> contained in a <value expression> simply contained in an <update source> or an <assigned row> contained in the <SQL routine body> of RD.

Modify SR29)k) as follows:

k) DELETE privilege on the table identified by the <target table> contained in a <merge statement> that contains a <merge delete specification> and that is contained in the <SQL routine body> of RD.

Modify SR29)l) as follows:

l) USAGE privilege on each domain, collation, character set, transliteration, and sequence generator whose name is contained in the <SQL routine body> of RD.


P02-13.5Data type correspondences

In SQL DataTtype column of Table 16 — Data type correspondences for Ada, a specification for character unit is missing at rows of CHARACTER VARYING and CHARACTER LARGE OBJECT.

SolutionModify a value of SQL data type column at the row of CHARACTER VARYING type as follows:

CHARACTER VARYING (L U)CHARACTER SET CS

Modify a value of SQL data type column at the row of CHARACTER VARYING type in Table 16 as follows:

CHARACTER LARGE OBJECT(L U)CHARACTER SET CS

See comment.

Page 32 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By



In C data type column of Table 17 — Data type correspondences for C, footnote reference number 1 appears twice at rows of CHARACTER LARGE OBJECT.

SolutionModify a value of SQL data type column at the row of CHARACTER LARGE OBJECT type in Table 17as follows:

struct {long hvn_reserved;unsigned long hvn_length;unit hvn_data[L1 * k];

} hvn1 2 3;

See comment.



In the third item of footnote of Table 17 — Data type correspondences for C, an undefined symbol AV appears instead of a defined symbol CV.

SolutionModify the third item of footnote of Table 17 as follows:

3 In a C value CV of this type, the length portion of CV is the field of CV called hvn_length, and the data portion of AV CV is the field of AV CV called hvn_data.

See comment.



In the 4th item of footnote ofTable 18 — Data type correspondences for COBOL, an undefined symbol AV appears instead of a defined symbol CV.

SolutionModify the 4th item of footnote of Table 18 as follows:

4 In a COBOL value CV of this type, the length portion of CV is the field of CV called hvn-LENGTH, and the data portion of AV CV is the field of AV CV called hvn-DATA..

See comment.



In the third item of footnote of Table 19 — Data type correspondences for Fortran, an undefined symbol AV appears instead of a defined symbol CV.

SolutionModify the third item of footnote of Table 19 as follows:

3 In a Fortran value FV of this type, the length portion of FV is the field of FV called hvn_LENGTH, and the data portion of AV FV is the

See comment.

Page 33 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

field of AV FV called hvn_DATA.P02-JPN-081 P02-JPN-115 4-Minor

EditorialP02-13.5Data type correspondences

According to Table 19 — Data type correspondences for Fortran, Fortran Data Type corresponding to SQL Data Type of BINARY VARYING is “None”. However, SR6)e) of Subclause 21.6 <embedded SQL Fortran program> provides Fortran variable declaration corresponding to host parameter data type of BINARY VARYING. Fortran data type for BINARY VARYING should be supplied as provided in SR6)g) of Subclause 21.6.

SolutionModify a value of Fortran data type column at the row of BINARY VARYING(L) type in Table 19 as follows:

NoneCHARACTER HVN (L+8)INTEGER*4 HVN_RESERVEDINTEGER*4 HVN_LENGTHCHARACTER HVN_DATA * LEQUIVALENCE (HVN(1), HVN_RESERVED)EQUIVALENCE (HVN(5), HVN_LENGTH)EQUIVALENCE (HVN(9), HVN_DATA)

See comment.


P02-14.5<fetch statement>

While the term “arbitrary site” used in in SR9)b)iii)1) of Subclause 14.5, “temporary site” is used inSR3)b)ii)1) of Subclause 14.7, “14.7 <select statement: single row>”, in SR11)a) of Subclause 14.14, “<set clause list>”, and so on.

SolutionModify SR9)b)iii)1)as follows:

1) If TS1i contains a <simple value specification>, then the Syntax Rules of Subclause 9.2, “Store assignment”, are applied with an arbitrary a temporary site whose declared type is the declared type of TS1i as TARGET and CSi as VALUE.

See comment.


P02-14.5<fetch statement>

An unexpected comma appears in SR9)b)v.Solution

Modify SR9)b)v)as follows:

v) For each <target specification> TS2i, 1 (one) ≤ i, ≤ NTS, that is an <embedded variable specification>, the Syntax Rules of Subclause 9.1, “Retrieval assignment”, are applied

See comment.

Page 34 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

with TS2i as TARGET and CSi as VALUE.P02-JPN-084 4-Minor

EditorialP02-14.8<delete statement: positioned>,P02-14.13<update statement: positioned>

A wording “implicit qualifier of TN” appears in SR10) of Subclause 14.8 and in SR10) of Subclause 14.13, “<update statement: positioned>”. It should be “<schema name> of TN”, just like 14.10, because <schema name> is more specific.

SolutionModify SR10) of 14.8 as follows:

10) The schema identified by the explicit or implicit qualifier<schema name> of TN shall include the descriptor of LUT.

Modify SR10) of 14.13 as follows:

10) The schema identified by the explicit or implicit qualifier<schema name> of TN shall include the descriptor of LUT.

See comment.


P02-14.8<delete statement: positioned>

While a symbol CN appears in NOTE 512 in SR11), the symbol used in a description in SR11) is COR.


NOTE 512 — CN COR has no scope.

See comment.


P02-14.11<insert statement>

It seems that the last line of SR6) needs “is” between “DEFAULT” and “equal”.


6) An <insert columns and source> that specifies DEFAULT VALUES is implicitly replaced by an <insert columns and source> that specifies a <contextually typed table value constructor> of the formVALUES (DEFAULT, DEFAULT, ..., DEFAULT)where the number of instances of “DEFAULT” is equal to the number of columns of T.

See comment.


P02-14.11<insert statement>

In application of Subclause 9.2, “Store assignment” in SR14, while a column is specified as the assignment target, a table value is specified for the assignment value. This means that

See comment.

Page 35 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

SR14) describes an incompatible store assignment. Solution

Modify SR14) as follows:

14) For each column of T identified by the <column name> in the <insert column list>, Tthe Syntax Rules of Subclause 9.2, “Store assignment”, are applied with corresponding the columns of T as TARGET and the corresponding column of QT as VALUE.


P02-14.12<merge statement>

Although the rule that an <ONLY spec> is added implicitly for a viewed table is removed in case of an insert statement in SQL:2011, the same rule still remain in case of a merge statement as SR7).




The symbol “DSC” in SR20) is not in italic form.Solution

Modify the lead text of SR20) as follows:

20) Let DSC DSC be the <search condition> immediately contained in <merge statement>.

See comment.



Although AR1)b) is rules in terms of current privileges, AR1)d)ii) describe a rule for applicable privileges.

SolutionModify AR1)d)ii) as follows:

ii) If <merge delete specification> is specified, then the applicable current privileges for A shall include DELETE for T.

See comment.



Just one occurrence of “open cursor” appears without a symbol CR in GR6)a)iv), which reads:

iv) If any row in the set of object rows has been marked for deletion by any <delete statement: positioned>, <dynamic delete statement: positioned>, or <preparable dynamic delete statement: positioned> that identifies some open cursor CR or updated by any <update statement: positioned>, <dynamic update statement: positioned>, or

Page 36 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

<preparable dynamic update statement: positioned> that identifies some open cursor, then a completion condition is raised: warning — cursor operation conflict.

However, “open cursor” is always appears with CR in all other similar rule. Although AR1)b) is rules, such as GR8) of Subclause 14.14 <update statement: searched>:

8) If any row in the set of object rows has been marked for deletion by any <delete statement: positioned>,<dynamic delete statement: positioned>, or <preparable dynamic delete statement: positioned> that identifies some open cursor CR or updated by any <update statement: positioned>, <dynamic update statement: positioned>, or <preparable dynamic update statement: positioned> that identifies some open cursor CR, then a completion condition is raised: warning — cursor operation conflict.




In GR6)a)vi)2)B), the sentence “T is a viewed table” following “otherwise,” does not make sense.

SolutionModify GR6)a)vi)2)B) as follows:

B) Otherwise,If T is a viewed table and, then the General Rules of Subclause 15.9, “Effect of deleting some rows from a viewed table”, are applied with TT as VIEW NAME.

See comment.


P02-14.14<update statement: searched>

An undefined symbol UPS appears in SR8). If UPS is intended to be the update statement of this Subclause, symbol USS defined in SR1) should be used.


8) If UPSUSS is contained in a <triggered SQL statement>, then SC shall not contain a <value specification> that specifies a parameter reference.

See comment.


P02-14.14<update statement:

The table identified by “<correlation name>s or <table or query name>” in GR5)a) should be clarified just likeGR5)b),

See comment.

Page 37 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

searched> which reads:

a) If TT contains ONLY, then SC is effectively evaluated for each row of T with the exposed <correlation name>s or <table or query name>s bound to that row, and the subject rows are those rows for which the result of SC is True and for which there is no subrow in a proper subtable of T. SC is effectively evaluated for each row of T before updating any row of T.

b) Otherwise, SC is effectively evaluated for each row of T with the exposed <correlation name>s or <table or query name>s of TT bound to that row, and the subject rows are those rows for which the result of SC is True. SC is effectively evaluated for each row of T before updating any row of T.


a) If TT contains ONLY, then SC is effectively evaluated for each row of T with the exposed <correlation name>s or <table or query name>s of TT bound to that row, and the subject rows are those rows for which the result of SC is True and for which there is no subrow in a proper subtable of T. SC is effectively evaluated for each row of T before updating any row of T.


P02-14.16<temporary table declaration>

A description “U does not contain a table” in GR1 is incorrect, since U is a schema name and what does not contain a table is a schema itself, not its name.

SolutionModify GR1) as follows:

1) Let U be the implementation-dependent <schema name> of the schema that contains the declared local temporary table such that the schema identified by U does not contain a table whose <table name> is equivalent to TN.

See comment.


P02-15.10Effect of inserting tables into base tables

The term “data type “ in GR2)b)ii) should be “declared type”, just like in GR2)c)ii).

SolutionModify GR2)b)ii) as follows:

See comment.

Page 38 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

ii) Let NV be the transaction timestamp of the current SQL-transaction. Let DT be the data declared type of the system-time period start column of T. Let NVV be the result of CAST (NV AS DT)


P02-15.10Effect of inserting tables into base tables

A period is missing at the end of GR2)a)iii), GR2)b)iii), and GR2)c)iii).

SolutionSupply a period at the end of GR2)a)iii), GR2)b)iii), and GR2)c)iii), respectively.

See comment.


P02-15.13Effect of replacing rows in base tables

The unexpected hyphen appears between “system-time” and “period” in GR9)a)i).

SolutionModify GR9)a)i) as follows:

i) Let START be the system-time-period start column of T and let END be the system-time period end column of T. Let DT be the declared type of START.:

See comment.


P02-15.13Effect of replacing rows in base tables

The word “constraint” is missing immediately before “checking” in GR10)d)ii).

SolutionModify GR10)d)ii) as follows:

ii) The following <insert statement> is effectively executed without further Access Rule and constraint checking:

See comment.


P02-15.19Execution of triggers

A condition name “modify table modified by data change delta table” in GR5)h) is incorrect. In Table 33 — SQLSTATE class and subclass values, the condition name whose subcondition name is “modify table modified by data change delta table” is “prohibited statement encountered during trigger execution”.

SolutionModify GR5)h) as follows:

h) If TR is an AFTER trigger and the subject table restriction flag of the current SQL-session context is set to True, and if during the execution of TR any attempt is made to insert a row, update a row, or delete a row in a table whose name is included in the restricted subject table name list included in the current SQL-session context, then an exception condition

See comment.

Page 39 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

is raised: prohibited statement encountered during trigger execution — modify table modified by data change delta table.

Delete the entry for “prohibited statement encountered during trigger execution” from Index.


P02-15.19 Execution of triggers

An undefined symbol RSC appears in GR5)j).Solution

Modify GR5) as follows:

a) The General Rules of Subclause 23.2, “Pushing and popping the diagnostics area stack”, are applied with “PUSH” as OPERATION and the diagnostics area stack in the current SQL-session context CSC as STACK.

…..j) The General Rules of Subclause 23.2, “Pushing and popping the

diagnostics area stack”, are applied with “POP” as OPERATION and the diagnostics area stack in RSC CSC as STACK.

See comment.


P02-16.2<return statement>

In application of Subclause 9.2, “Store assignment” in SR4), data type of a value is specified as parameter VALUE. However, of Subclause 9.2 requires a value itself as parameter VALUE,not a data type of a value.


4) The Syntax Rules of Subclause 9.2, “Store assignment”, are applied with an item of the data type RDT as TARGET and the declared type of VE as VALUE.

See comment.


P02-20.4<get descriptor statement>

An incorrect term “SQL descriptor” appears in GR2). The correct term is “SQL descriptor area”.


2) If the <item number> specified in a <get descriptor statement> is greater than the value of <occurrences> specified when the SQL descriptor area identified by the <descriptor name> was allocated or less than 1 (one), then an exception condition is raised: dynamic SQL error —

See comment.

Page 40 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

invalid descriptor index.P02-JPN-104 4-Minor

EditorialP02-20.4<get descriptor statement>

An incorrect term “item information area” appears in GR7). The correct term is “item descriptor area”. In addition, a word “item” at the end of 5th sentence is not expected, since the referent from <allocate descriptor statement> etc is an SQL descriptor and is not an item.


7) A <get descriptor statement> retrieves values from the SQL descriptor area specified by <descriptor name>. The values retrieved are specified by the <get descriptor information>. If <get descriptor information> specifies one or more <get header information>s, then the values retrieved are those identified by the <header item name>s contained in those <get header information>s. If <get descriptor information> specifies one or more <get item information>s, then the values retrieved are those identified by the <descriptor item name>s contained in those <get item information>s in the item informationdescriptor area identified by <item number>. For each item, the value that is retrieved is the one established by the most recently executed <allocate descriptor statement>, <set descriptor statement>, or <describe statement> that references the specified SQL descriptor area and item. The value retrieved by a <get descriptor statement> for any field whose value is undefined is implementation-dependent.

See comment.


P02-20.5<set descriptor statement>

GR5) describes an assignment of header information. However, according to GR4), V, which is specified for an assignment value, is the value of <simple value specification 2> for item information.


5) For each <set header information> specified, the General Rules of Subclause 9.2, “Store assignment”, are applied with the field identified by <header item name> as TARGET and Vthe value of <simple value specification 1> as VALUE.

See comment.

P02-JPN-106 4-Minor P02-20.6 The description “DP is X1 or X2” does not make sense in the See comment.Page 41 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Editorial <prepare statement>

lead texts in GR5)a)ix), x) and xi)2).Solution

Modify the lead text of GR5)a)ix) as follows:

ix) If DP is either X1 or X2 in a <value expression> of the form “X1 || X2” and DP is X1 or X2, then

Modify the lead text of GR5)x) as follows:

x) If DP is either X1 or X2 in a <value expression> of the form “X1 * X2” or “X1 / X2” and DP is X1 or X2, respectively, then

Modify the lead text of GR5)xi)2) as follows:

2) Otherwise, if DP is X1 or X2, thenP02-JPN-107 4-Minor

EditorialP02-20.6<prepare statement>

In GR5)a)xviii)1)D), “<match predicate part2>” is missing..Solution

Modify GR5)a)xviii)1)D) as follows:

D) The set consisting of the declared row type of a <table subquery> simply contained in an <in predicate part 2>, <match predicate part2>, or <quantified comparison predicate part 2> simply contained in CE.

See comment.


P02-20.6<prepare statement>

Notation RV1(RV2) still remain GR5)a)xxiv)2). Solution

Modify GR5)a)xxiv)2) as follows:

2) Otherwise, if DP is simply contained in RV1 (or RV2), then DT is the declared type of the first field of RV2 (or RV1) , respectively.

See comment.


P02-20.16 <allocate received cursor statement>

While the cursor name of a received cursor was an extended cursor name until SQL:2008, it was changed to a cursor name in SQL:2011. Some implementation had provided a received cursor with an extended cursor name before that change of specification was made. A received cursor with an extended cursor name should be provided optionally in the current standard.

Page 42 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By



P02-20.23<preparable dynamic delete statement: positioned>

Although a symbol TN is defined for the name of LUT in SR2)b), it is defined for the name of a target table in SR2)c)ii). The definition for LUT should be in SR2)c)i), which is in the same level as SR2)c)ii).

SolutionModify SR2)b) and c) as follows:

b) Let QE be the <query expression> simply contained in the <cursor specification> of the result set descriptor of CR. Let LUT be the target leaf underlying table of QE. Let TN be the name of LUT.

c) Case:i) If <target table> is not specified, then let TN be the name of LUT.Case:1) If the <table reference> that references LUT specifies ONLY, then the <target table>ONLY ( TN )is implicit.

2) Otherwise, the <target table>TNis implicit.

ii) Otherwise, let TN be the <table name> contained in <target table>. TN shall identify LUT.

See comment.


P02-20.25<preparable dynamic update statement: positioned>

Although a symbol TN is defined for the name of LUT in SR2)b), it is defined for the name of a target table in SR2)c)ii). The definition for LUT should be in SR2)c)i), which is in the same level as SR2)c)ii). In addition, a symbol CR defined in in SR2)a) should be used instead of “the cursor identified by <preparable dynamic cursor name>”.

SolutionModify SR2)b) and c) as follows:

b) Let QE be the <query expression> simply contained in the <cursor specification> of the result set descriptor of the cursor identified by <preparable dynamic cursor name>CR. Let LUT be the target leaf underlying table of QE.

See comment.

Page 43 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Let TN be the name of LUT.c) Case:

i) If <target table> is not specified, then let TN be the name of LUT.Case:1) If the <table reference> that references LUT specifies ONLY, then the <target table>ONLY ( TN )is implicit.

2) Otherwise, the <target table>TNis implicit.

ii) Otherwise, let TN be the <table name> contained in <target table>. TN shall identify LUT.


P02-21.1<embedded SQL host program>

A undefined symbol “GUOk” appears in SR22)l)i)6)J). The correct symbol is “GNOk” defined in SR22)l)i)6)G) since “GUOk” is used as a group name”

SolutionModify SR2)l)i)6)J) as follows:

J) For every k, 1 (one) ≤ k ≤ b, the Syntax Rules of Subclause 9.21, “Determination of a from-sql function”, are applied with TUOk as TYPE and GUOk GNOk as GROUP. There shall be an applicable from-sql function FSFOk identified by <routine name> FSONk. Let TROk be the result data type of FSFOk. TSOk shall be assignable to TROk.

See comment.


P02-21.1<embedded SQL host program>

The symbol “GNIO” appears without subscript in SR22)l)i)6)K).Solution

Modify SR22)l)i)6)K) as follows:

K) For every l, 1 (one) ≤ l ≤ c, the Syntax Rules of Subclause 9.21, “Determination of a from-sql function”, are applied with TUIO as TYPE and GNIOl as GROUP. There shall be an applicable from-sql function FSFIOl identified by <routine name> FSIONl. Let TRIOl be the result data type of FSFIOl. TSIOl shall be assignable to TRIOl.

See comment.


P02-21.3<embedded SQL Ada

The term “maximum length” in SR4)c)i) and iv) is appropriate rather than “length”, because the length of a large object type is variable.

See comment.

Page 44 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

program> SolutionModify SR4)c)i) as follows:

i) If ATS is <Ada CLOB variable>, then the <host parameter data type> of HV is CHARACTER LARGE OBJECT, with maximum length specified by <character large object length> and character set specified by <character set specification>. If <character set specification> is omitted, then the character set is implementation-defined.

Modify SR4)c)iv) as follows:

iv) If ATS is <Ada VARBINARY variable>, then the <host parameter data type> of HV is BINARY VARYING with maximum length specified by <length>.


P02-21.3<embedded SQL Ada program>

A wording “reference type identified by RT” in SR6) is not reasonable, because the data type identified by a <referenced type> is a reference type but a referenced type.


6) The reference data type identified by the <referenced type> contained in the <reference type> contained in an <Ada REF variable> is called the referenced type of the reference.

See comment.


P02-21.4<embedded SQL C program>

The last sentence of SR4)b)iv) is redundant, because a description about default character set in the case of CHARACTER LARGR OBJECT type and NATIONAL CHARACTER LARGR OBJECT is provided in the last sentence of SR4)b)i).

SolutionModify SR4)b)iv) as follows:

iv) If <C CLOB variable> or <C NCLOB variable> is specified, then the <host parameter data type> of HV is CHARACTER LARGE OBJECT or NATIONAL CHARACTER LARGE OBJECT, respectively, with maximum length specified by <character large object length>, and with character set specified by the <character set specification>. If there is no <character set specification>, then the character set is

See comment.

Page 45 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

implementation-defined.P02-JPN-117 4-Minor

EditorialP02-21.4<embedded SQL C program>

A wording “reference type identified by RT” in SR4)c)x) is not reasonable, because the data type identified RT is RT itself.

SolutionModify SR4)c)x) as follows:

x) 14 If CVS is <C REF variable>, then the <host parameter data type> of HV is RT, where RT is the <reference type>. The reference data type identified by the <referenced type> contained in RT is called the referenced type of the reference.

See comment.


P02-21.5<embedded SQL COBOL program>

The term “maximum length” in SR4)d)iii) is appropriate rather than “length”, because the length of a large object type is variable.

SolutionModify SR4)d)iii) as follows:

iii) If CTS contains <COBOL BLOB variable>, then the <host parameter data type> of HV is BINARY LARGE OBEJCT, with maximum length specified by the <large object length>.

See comment.



A wording “reference type identified by RT” in SR4)d)x) is not reasonable, because the data type identified by a <referenced type> is a reference type but a referenced type.

Solution

Modify SR4)d)x) as follows:

x) 14 If CTS contains <COBOL REF variable>, then the <host parameter data type> of HV is the <reference type> RT contained in CTS. The reference data type identified by the <referenced type> contained in RT is called the referenced type of the reference.

See comment.



The term “SQL data type” in CR12) should be “<host parameter data type>” which is used in syntax rules.


12) Without Feature T071, “BIGINT data type”, in conforming

See comment.

Page 46 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

SQL language, the SQL data type <host parameter data type>that is equivalent to a <COBOL integer type> shall not be BIGINT.


P02-21.6<embedded SQL Fortran program>

A wording “reference type identified by the <referenced type>” in SR5)g)xi) is not reasonable, because the data type identified by a <referenced type> is a reference type but a referenced type.

SolutionModify SR5)g)xi) as follows:

xi) 14 If FTS contains <Fortran REF variable>, then the <host parameter data type> of HV is RT, where RT is the <reference type> contained in FTS. The reference data type identified by the <referenced type> contained in the <reference type> contained in RT is called the referenced type of the reference.

See comment.


P02-21.6<embedded SQL Fortran program>

The declaration to fill out any gap in a variable area is necessary in SR6)g), just like SR6)e) which reads:

CHARACTER HVN (L+8)INTEGER*4 HVN_RESERVEDINTEGER*4 HVN_LENGTHCHARACTER HVN_DATA * LLEQUIVALENCE (HVN(1), HVN_RESERVED)EQUIVALENCE (HVN(5), HVN_LENGTH)EQUIVALENCE (HVN(9), HVN_DATA)

SolutionModify SR6)g) as follows:

g) The syntaxSQL TYPE IS VARBINARY ( L )for a given <Fortran host identifier> HVN shall be replaced by

CHARACTER HVN (L+8)INTEGER*4 HVN_RESERVEDINTEGER*4 HVN_LENGTHCHARACTER HVN_DATA * LEQUIVALENCE (HVN(1), HVN_RESERVED)EQUIVALENCE (HVN(5), HVN_LENGTH)EQUIVALENCE (HVN(9), HVN_DATA)

See comment.

Page 47 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

in any <Fortran VARBINARY variable>.P02-JPN-123 4-Minor

EditorialP02-21.7<embedded SQL MUMPS program>

A wording “reference type identified by RT” in SR4)c)ii) is not reasonable, because the data type identified by a <referenced type> is a reference type but a referenced type.

SolutionModify SR4)c)vii) as follows:

vii) If MVD contains <MUMPS REF variable>, then let RT be the <reference type> contained in MVD. The <host parameter data type> of HV is RT. The reference data type identified by the <referenced type> contained in RT is called the referenced type of the reference.

See comment.


P02-21.8<embedded SQL Pascal program>

The incorrect wording “<Pascal host identifier> contained in PTS” is included in the lead text of SR4), which lead.

4) A <Pascal variable definition> PVD defines one or more <Pascal host identifier>s. Let PTS be the <Pascal type specification> contained in PVD, let PHI be a <Pascal host identifier> contained in PTS, and let HV be the host variable corresponding to PHI.

The symbol PTS denotes <Pascal type specification>. However, <Pascal type specification> specify a data type and does not contain <Pascal host identifier>. PVD shall be used instead of PTS.


4) A <Pascal variable definition> PVD defines one or more <Pascal host identifier>s. Let PTS be the <Pascal type specification> contained in PVD, let PHI be a <Pascal host identifier> contained in PTS PVD, and let HV be the host variable corresponding to PHI.

See comment.



The term “maximum length” in SR4)f)i) and iii) is appropriate rather than “length”, because the length of a large object type is variable.

Solution

See comment.

Page 48 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Modify SR4)f)i) as follows:

i) If PTS contains <Pascal CLOB variable>, then the <host parameter data type> of HV is CHARACTER LARGE OBJECT, with maximum length specified by the <character large object length>, and with character set specified by <character set specification>. If <character set specification> is not specified, then the character set is implementation-defined.

Modify SR4)f)iii) as follows:

iii) If PTS contains <Pascal BLOB variable>, then the <host parameter data type> of HV is BINARY LARGE OBJECT, with maximum length specified by the <large object length>.



A wording “reference type identified by RT” in SR4)f)x) is not reasonable, because the data type identified by a <referenced type> is a reference type but a referenced type.

SolutionModify SR4)f)x) as follows:

x) 14If PTS contains <Pascal REF variable>, then the <host parameter data type> of HV is the <reference type> RT contained in PTS. The reference data type identified by the <referenced type> contained in RT is called the referenced type of the reference.

See comment.


P02-21.8<embedded SQL Pascal program>P02-Annex A,SQL Conformance Summary

CR10) implies CR7) and CR8). The duplicate parts should be excluded from CR10).

7) Without Feature T041, “Basic LOB data type support”, conforming SQL language shall not contain a <Pascal BLOB variable>.

8) Without Feature T041, “Basic LOB data type support”, conforming SQL language shall not contain a <Pascal CLOB variable>.

9) …..10) Without Feature T041, “Basic LOB data type support”, conforming SQL language shall not contain a <Pascal BLOB

See comment.

Page 49 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

variable>, <Pascal CLOB variable>, <Pascal CLOB locator variable>.

SolutionModify CR10) of Subclause 21.8 as follows:

10) Without Feature T041, “Basic LOB data type support”, conforming SQL language shall not contain a <Pascal BLOB variable>, <Pascal CLOB variable>, <Pascal CLOB locator variable>.

Modify 189)k)iv) of Annex A as follows:

iv) Without Feature T041, “Basic LOB data type support”, conforming SQL language shall not contain a <Pascal BLOB variable>, <Pascal CLOB variable>, <Pascal CLOB locator variable>.


21.9 <embedded SQL PL/I program>

The description in SR4)d) that the host parameter data type for PL/I type fixed binary is inappropriate

SolutionModify SR4)d) as follows:

d) If PTS is <PL/I type fixedfloat binary>, then the <host parameter data type> of HV is FLOAT with the same <precision>.

See comment.



A wording “reference type identified by RT” in SR4)e)xi) is not reasonable, because the data type identified by a <referenced type> is a reference type but a referenced type.

SolutionModify SR4) e)xi) as follows:

xi) 14 If PTS contains <PL/I REF variable>, then the <host parameter data type> of HV is RT, where RT is the <reference type> contained in PTS. The reference data type identified by RT is called the referenced type of the reference.

See comment.



The description about an optional <character representation> is nothing anywhere in syntax rules. It was included in SQL:2008.

Page 50 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By




The term “SQL data type” in CR13) should be “<host parameter data type>” which is used in syntax rules.


13) Without Feature T071, “BIGINT data type”, in conforming SQL language, the SQL data type <host parameter data type> that is equivalent to a <PL/I type fixed binary> shall not be BIGINT.

See comment.


P02-22.1<direct SQL statement>

The term “access mode” in GR6)b)iv) is a little bit incorrect. “transaction access mode” is correct one.

Solution

Modify GR6)b)iv as follows:

iv) If S contains an <SQL schema statement> and the transaction access mode of the current SQL-transaction is read-only, then an exception condition is raised: invalid transaction state — read-only SQLtransaction, no further subrules of this General Rule are evaluated, and evaluation continues with the next General Rule.

See comment.


P02-25.3Implied feature relationships of SQL/Foundation

The row with “Feature ID” column value of “F863” and that of “F862” are in reverse order.

SolutionSwap the row with “Feature ID” column value of “F863” and that of “F862”

See comment.


P02-25.3Implied feature relationships of SQL/Foundation

In Table 35 “Table 35 — Implied feature relationships of SQL/Foundation “, the “Feature Name” column value of the row whose “Feature ID” column value is “F867” and whose “Implied Feature ID” column value is “F850” is incorrect.

SolutionModify the “Feature Name” column value of the row whose “Feature ID” column value is “F867” and whose “Implied Feature ID” column value is “F850” in Table 35 as follows:

See comment.

Page 51 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

Nested <fetch first clause> in <query expression>FETCH FIRST clause: WITH TIES option


P02-Annex.BImplementation-defined elements

No corresponding descriptions to the description of item 1)a) and b) are in Subclause 4.2.2, “Comparison of character strings”. The corresponding descriptions are in Subclause 4.2.1, “Introduction to character strings”. The title of item 1) shall be 4.2.1, “Introduction to character strings”

SolutionModify 1) as follows:

1) Subclause 4.2.2, “Comparison of character strings” 4.2.1, “Introduction to character strings”:a) The specific character set associated with the subtype of character string represented by the <key word>s NATIONAL CHARACTER is implementation-defined.

b) The circumstances in which conversion of non-UCS character string expressions from one character set to another is automatic are implementation-defined.

See comment.



The item 20)a) of Annex B states that output parameters, the value returned from the program, the value of the SQLSTATE, and the value of the message text from the values assigned by the program to the effective SQL parameter list are obtained in an implementation-defined manner in an invocation of an external routine with parameter style GENERAL. However, according to 4th and 5th sentence of 6th paragraph of 4.33.2, “Characteristics of SQL-invoked routines”, quoted below, obtaining such values to the effective SQL parameter list is the manner in in an invocation of an external routine with parameter style SQL. A manner of obtaining those values is implementation-defined in an invocation of an external routine with parameter style GENERAL.

After the execution of that program, if the parameter passing style of the SQL-invoked routine is SQL, then the SQL-implementation obtains the values for output parameters (if any), the value (if any) returned from the program, the value of the SQLSTATE, and the value of the message text (if any) from the values assigned by the program to the effective SQL parameter list. If the parameter passing style of the SQL-

See comment.

Page 52 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

invoked routine is GENERAL, then such values are obtained in an implementation-defined manner.

Therefore, the phrase of “from the values assigned by the program to the effective SQL parameter list” should be removed.

SolutionModify 20)a) as follows:

a) After the execution of the program identified by the <routine body> of an external routine, if the parameter passing style of that routine is GENERAL, then the values for output parameters (if any), the value (if any) returned from the program, the value of the SQLSTATE, and the value of the message text (if any) from the values assigned by the program to the effective SQL parameter list are obtained in an implementation-defined manner.



While the item 24)a) mentions only information about an exception condition, that about a completion condition is also mentioned in 5th paragraph of Subclause 4.36 “Diagnostics area”., which reads:

At the beginning of the execution of any <SQL procedure statement> that is not an <SQL diagnostics statement>, the first diagnostics area is emptied. An implementation places information about a completion condition or an exception condition reported by SQLSTATE into a vacant condition area in this diagnostics area. If other conditions are raised, the extent to which these cause further condition areas to become occupied is implementation-defined.

SolutionModify24)a) as follows:

a) When information about a completion condition or an exception condition reported by SQLSTATE is placed into a vacant condition area in this diagnostics area, the extent to which other conditions that may be raised cause further condition areas to become occupied is implementation-defined.

See comment.

Page 53 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By



The implementation-defined item described in the prior paragraph to the last of Subclause 4.44.1, “General description of triggers” is missing in Annex B.

SolutionInsert the following item immediately after item 30) and increase the number of every item after the inserted item:

31) Subclause, 4.44.1, “General description of triggers”a) The order of execution of a set of triggers is

ascending by value of their timestamp of creation in their descriptors, such that the oldest trigger executes first. If one or more triggers have the same timestamp value, then their relative order of execution is implementation-defined.

See comment.



No corresponding rule to the description of item 68)a) is in Subclause 11.6, “<table constraint definition>”. The corresponding rule is GR2) of Subclause 11.8, “<referential constraint definition>”. The title of item 68) shall be 11.8, “<referential constraint definition>”.


68) Subclause 11.6, “<table constraint definition>” 11.8, “<referential constraint definition>”:

a) The ordering of the lists of referencing column names and referenced column names in a referential constraint descriptor is implementation-defined, but shall be such that corresponding column names occupy corresponding positions in each list.

See comment.



The item 76)b) includes the description that an <SQL-client module definition> invokes an <externally-invoked procedure>.

b) It is implementation-defined whether or not an <SQL-client module definition> that contains the <externally-invoked procedure> with an explicit <module authorization identifier> MAI that is not equivalent to the SQL-session <authorization identifier> SAI can invoke <externally-invoked procedure> s in an <SQL-client module definition>

Page 54 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

with an explicit <module authorization identifier> MAI.

This is not appropriate, because an invoker of an <externally-invoked procedure> is <authorization identifier> according to GR6)a) of , the corresponding rules to item 76)b), which reads:

6) If the <SQL-client module definition> that contains the <externally-invoked procedure> has an explicit <module authorization identifier> MAI that is not equivalent to the SQL-session <authorization identifier> SAI, then:a) Whether or not SAI can invoke <externally-invoked procedure>s in an <SQL-client module definition> with explicit <module authorization identifier> MAI is implementation-defined, as are any restrictions pertaining to such invocation.

The description of an item in Annex B and the corresponding rule shall be consistent with each other.



P02-Annex.CImplementation-dependent elements

The term “implementation-defined “ appears in 6)c) instead of “implementation-dependent”.

SolutionModify 6)c) as follows:

c) The maximum number of diagnostics area in a diagnostics area stack is implementation-defined dependent.

See comment.



The item 37)a) includes the description that a referenceable view whose reference representation is derived. This is a little bit inappropriate, because “derived representation” is an alternative of a reference type specification, and a reference type specification is a property of a reference type, not of a table.


a) The expression used to compute the value of the self-

See comment.

Page 55 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

referencing column of a referenceable view whose reference type has derived representation is derived is implementation-dependent.



The symbol PORMS in 41)a) does not appear in the corresponding rule SR6)a) of Subclause 11.57, “<add overriding method specification>”, which reads:

a) If POVMS does not specify <specific method name>, then an implementation-dependent <specific method name> is implicit whose <schema name> is equivalent to SN.


a) If PORMS POVMS does not specify <specific method name>, then an implementation-dependent <specific method name> is implicit whose <schema name> is equivalent to SN.

See comment.



The term “constraint” in 66)a) is different from the term at the same position on the corresponding rule to GR2)a) of Subclause 21.1,”<direct SQL statement>”, which reads:

a) A <rollback statement> or a <commit statement> is effectively executed. If an unrecoverable error has occurred, or if the direct invocation of SQL terminated unexpectedly, or if any enforced constraint is not satisfied, then a <rollback statement> is performed. Otherwise, the choice of which of these SQL-statements to perform is implementation-dependent. The determination of whether a directinvocation of SQL has terminated unexpectedly is implementation-dependent.


a) A <commit statement> or a <rollback statement> is executed. If an unrecoverable error has occurred, or if the direct invocation of SQL terminated unexpectedly, or if any enforced constraint is not satisfied, then a <rollback statement> is performed. Otherwise, the choice of which of these SQL-statements to perform is implementation-

See comment.

Page 56 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

dependent. The determination of whether a direct invocation of SQL has terminated unexpectedly is implementation-dependent.


P02-Annex.EIncompatibilities with ISO/IEC 9075:2008

The last sentence of item 3) is incompletely finished.Solution

Modify 3) as follows:

3) In ISO/IEC 9075-2:2008, Feature T052, “MAX and MIN for row types” provided support for MAX and MIN operations on values of row types. In this edition of this part of ISO/IEC 9075, that feature has been removed and the support provided inherently in the specification has been removed.

See comment.



The term “Feature Code” in item 7) is incorrect. The correct term is “Feature ID”.


7) In ISO/IEC 9075-2:2008, ISO/IEC 9075-4:2008, and ISO/IEC 9075-11:2008, Feature CodesIDs T322 and T332 were not used consistently; they identified three different Features in various parts of ISO/IEC 9075. In this edition of ISO/IEC 9075, three Feature CodesIDs (T322, T332, and T341) have been used consistently to identify those three Features.

See comment.



Before the second occurrence of “9075-2” is “ISO/IEC” is missing in item 11).


11) In ISO/IEC 9075-2:2008, the length portion of a host language data structure for a CHARACTER LARGE OBJECT was measured in characters when moving from the host language to the SQL-server, but in octets in the reverse direction. In this edition of ISO/IEC 9075-2, the length portion is measured in the same units in either direction, either characters or octets, depending on the <char length units> of the declared type.

See comment.


P02-Annex.FSQL feature taxonomy

The row with “Feature ID” column value of “F673” does not found in Table 39 — Feature taxonomy for optional features.

See comment.

Page 57 of 47 2023-05-17


#Cmnt

IDSeeAlso Severit


Addressed By

SolutionInsert a row with number of “119”, “Feature ID” column value of “F673” and “Feature Name” column value of “Reads SQL-data routine invocations in CHECK constraints” immediately after the row with number “118” and increase the number of every row after the inserted row.


Index While the entries for “fetch call” and “close call” are included in Index, that for “open call” is not.

SolutionInsert the entry for “open call” into Index.

See comment.


P02-No specific location

All Possible Problems and Editor’s Notes must be satisfactorily resolved and all problems discovered during the course of the ballot resolution process must be satisfactorily resolved.


Page 58 of 47 2023-05-17

Template for comments and secretariat observations Date: Document:

1 2 (3) 4 5 (6) (7)

MB1 Clause No./Subclause

No./Annex

(e.g. 3.1)

Paragraph/Figure/Tabl

e/Note(e.g. Table

1)

Type of

com-ment

2

Comment (justification for change) by the MB Proposed change by the MB Secretariat observationson each comment submitted

US P02-03.01.06, Definitions provided in Part 2

te The definition of row pattern variable misses the case of a primary row pattern variable that has no definition in a <row pattern definition>.

None provided with comment.

US P02-04.01.04, Data type terminology

te There are now two conflicting definitions of array-ordered and multiset-ordered (see STR-033 and BHX-062r1).


US P02-04.15.01, Introduction to tables

ed Penultimate paragraph defines degree and cardinality of a table, but the words are not italicized.

Edit as follows:

The degree degree of a table, and the degree of each of its rows, is the number of columns of that table. The number of rows in a table is its cardinality cardinality.

US P02-04.15.10, Operations involving tables

te This subclause might be wordsmithed to better describe the primary effect of a data change operation on a view with an INSTEAD OF trigger. Currently we have the statement “The effect of an SQL-data change statement on a viewed table is specified by the General Rules of Subclause 15.9, “Effect of deleting some rows from a viewed table”, Subclause 15.12, “Effect of inserting a table into a viewed table”, and Subclause 15.15, “Effect of replacing some rows in a viewed table”. Which is certainly true. Then later we read “The primary effect of a <delete statement: positioned> on a regular base table T or a derived table T is to delete exactly one specified row from T. The primary effect of a <delete statement: searched> on a base table T or a derived table T is to delete zero or more rows from T.” which is not true in the case of a trigger-deletable view. Similarly for trigger-updatable and trigger-insertable-into views.


1 MB = Member body (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **)2 Type of comment: ge = general te = technical ed = editorial NOTE Columns 1, 2, 4, 5 are compulsory.

page 1 of 90ISO electronic balloting commenting template/version 2001-10


1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


US P02-04.15.10, Operations involving tables

te This subclause concludes with a definition of the secondary effects of updating a table. The first bullet says “Leaf underlying tables of T, other than T itself, whose values might be subject to secondary effects”. This sentence seems to think that a table could be a leaf underlying table of itself, however the definition in 4.15.8 “Syntactic analysis of derived tables and cursors” does not permit that.


US P02-04.15.11, Identity columns

te The text describes the situation in which a value for an identity column is omitted from the INSERT statement; however, it does not describe what happens if the INSERT statement does have a value for the identity column.


US P02-04.24.02, General rules and definitions

te This Subclause defines “counterpart”; Subclause 6.26 <value expression> defines “underlying column”. These concepts have considerable overlap; perhaps one or the other could be deleted. Note that for the most part,

updatability is in terms of counterparts (7.15 <query specification> SRs) except that updatable UNIONs use underlying columns (7.16 <query expression>)


US P02-04.39.04, SQL-statements and transaction states

te First paragraph says that transaction initiation is "usually before execution of the SQL-statement". After HER-026r1, it seems that we can now say that transaction initiation is always before execution; see 13.5 <SQL procedure statement> GR 8) and 11)a). But what about <start transaction statement>, which has its own GR to initiate a transaction and does not need the one in 13.5? Note that <savepoint statement>, <commit statement> and <rollback statement> do not have GRs to initiate a transaction (see SIA-023 concerning these statements).





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


US P02-04.40.02, Privileges

te The description of privileges with an <action> containing a <column name list> seems to suggest that a single privilege can describe an INSERT, UPDATE, SELECT, or REFERENCES privilege for more than one column. However, 12.3 <privileges> SR 11) performs a syntactic transformation that removes the list of column names and substitutes a single privilege for each individual column. This transformation is critical to the behavior of <revoke statement> since the privilege dependency graph has to work at the granularity of individual column privileges.


US P02-04.41.07, Encompassing transactions

te Does this clause describe one scenario or two? The first paragraph is talking about an SQL-transaction that is part of an encompassing transaction. This seems to be the scenario in which an SQL-transaction is part of a distributed transaction. Then (second paragraph after the first set of bullets) it talks about SQL-transactions that affect more than one SQL-server. This is the reverse scenario, in which the SQL-transaction is itself distributed. Perhaps these scenarios should be more clearly distinguished, for example, by placing each in its own subclause.


US P02-04.44.02, Trigger execution

ed This subclause contains a definition of “SQL-update operation” which is never used in this subclause or anywhere else in Foundation. Perhaps this definition can be deleted.


US P02-05.03, <literal>

te GR 5) talks of "rounding or truncation" but does not say that it is implementation defined. A general hunt for “round” and “truncat” might be in order to look for all similar situations.


US P02-06.01, <data type>

te Two minor problems with <large object length>: Both of these problems can be solved by revising the BNF as follows:

<large object length> ::=




1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


A) Consider the following BNF:

<length> ::= <unsigned integer>

<large object length> ::=

<length> [ <multiplier> ]

| <large object length token>

If <large object length> is omitted, then <length> is omitted and one might expect SR 5) “If <length> is omitted, then a <length> of 1 (one) is implicit” to supply the default. However SR 8) “If <large object length> is omitted, then an implementation-defined <large object length> is implicit” should be applied.

B) SR 9)a) and 9)b) hypothesize a <large object length> that immediately contains an <unsigned integer>, but actually it is <length> that is immediately contained in <large object length>

<length> <unsigned integer> [ <multiplier> ]

| <large object length token>

US P02-06.01, <data type>

te SR 43) regarding <array type> says that <maximum cardinality> is the maximum cardinality of an array. It would be better to say that the value of <maximum cardinality> is the maximum cardinality.

Edit the second sentence of SR 43) as follows:

The value of the <maximum cardinality> immediately contained in AT is the maximum cardinality of a site of data type AT.

US P02-06.06, <identifier chain>

te SR 8)a)i)1) handles references to columns in the result of a <query expression>, so that they can be referenced by an ORDER BY clause. But as worded, the rule assumes that there is a single SELECT list in the <query expression>. This ignores the possibility of UNION, etc. Probably this rule is meant to apply only to simple table





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


queries, defined in 7.16 <query expression> SR 30)c).

US P02-06.07, <column reference>

te The classification of column references in SR 7)b) -- formerly just ordinary, within-group-varying and group-invariant, and recently expanded to cover row pattern matching -- does not handle column references contained in <window function>s. Note that 6.10 <window function> SR 2) permits an aggregate within a window function., but there is a syntactic transformation of grouped windowed queries in <query specification> SR 13) which moves the aggregate to an in-line view and the window function becomes a window function of a column output by that in-line view. After performing this transformation (if necessary) then 6.7 <column reference> SR 7)b)ii) will classify any <column reference in a <window function> as an "ordinary column reference". Therefore GR 1)a) applies to it. But this rule is designed to support just the current row, rather than the set of rows in a window frame. See 10.9 <aggregate function> GR 1)e) which expects to form a set of rows. We also need to look at the window functions that do not use <aggregate function>, such as LAG, LEAD, etc.


US P02-06.09, <set function specification>

te SR 3) defines “aggregated argument of a <set function specification>”. A search shows that there are a few instances of “aggregated argument” applied to <aggregate function> rather than <set function specification>, namely 6.11 <nested window function> Function and SR 1), and 10.9 <aggregate function> SR 13).


US P02-06.26, <value expression>

te Consider this example:

SELECT T.C





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


FROM (SELECT CURRENT_DATE FROM Emp) AS T(C)

The column of the <derived table> in the FROM clause is non-determinstic, according to SR 7)a). However there is no rule that T.C in the SELECT list is non-deterministic. Note that SR 7) prolog paragraph uses general containment, but general containment does not recurse through <derived table>, <lateral derived table>, etc.

US P02-06.42, <row pattern navigation expression>

ed This subclause would be better positioned with the other <nonparenthesized

value expression primary>s

Move the subclause to follow 6.25 <multiset element reference>.

US P02-07.06, <table reference>

te <data change delta table> is a powerful capability, whose idea is found in a paper entitled “Returning Modified Rows – SELECT Statements with Side Effects”, by Andreas Behm et.al., presented in the 30th VLDB conference in Toronto in 2004. However, the standard lacks an important part of the functionality in that paper, called INCLUDE columns. INCLUDE columns can be used to pass additional information, such as which branch in a MERGE statement is taken, from the data change statement out to the SELECT statement containing the <data change delta table>. <data change delta table> should be enhanced with INCLUDE columns as described in the VLDB paper.



te <table function derived table> only supports table functions whose output table has a row type that is known when the table function is defined. SQL should be able to support more general transformations, that can take as input a generic table (one whose row type is known at query time but not at DDL time) and produce a generic





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


table as its result.


te The merger with SQL/RPR (KRK-027) has overwritten some of the edits adopted in SXF-020; thus SR 19) has the older term “updatable” instead of the newer term “generally updatable”.



te SR 16)b)ii) prohibits FINAL TABLE with MERGE if the target table is a view with an INSERT or UPDATE INSTEAD OF trigger. Should there also be a prohibition if the view has an INSTEAD OF DELETE trigger? There is no new delta table for DELETE but if a MERGE fires an INSTEAD OF trigger on a DELETE then you don't know what the final delta table is; the trigger might perform an insert or update to the target view, for example.



te FINAL TABLE should be prohibited if the target table is a view that has a target underlying table that is trigger insertable-into, trigger updatable or trigger deletable, depending on the operation in the <data change delta table>.



te SR 10)c) pertains to <joined table> not contained in a <from clause>. This case does not exist. A search of the BNF shows that the only syntactic elements that can immediately contain <joined table> are <table reference> and <parenthesized join table>, and these can only be reached inside a <from clause>. (I think the case was possible once when <joined table> was allowed as an operand of a <query expression> operator such as UNION, but that possibility was deleted.)



te SR 10)b) pertains to the scope of table references in a MERGE statement. Is this statement still correct, in view of the enhancements to MERGE? For example, SR 10)b) refers to “the <search condition>” as if there were only one, but there are now three places that a <search





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


condition> can be nested in a MERGE statement.


te The rules regarding insertable-into are not as cleanly worded as the rules regarding simply/generally/effectively updatable. Thus SR 19)a) says that certain kinds of <table reference> are not updatable, but does not say whether they are insertable-into. SR 21), on the other hand, says that <data change delta table> is not any kind of updatable or insertable-into. Note that by 7.15 <query specification> SR 30), being effectively updatable is a precondition for being insertable-into.



ed GR 2)c) has a nested Case structure that can be flattened to a single Case.

Delete subrule “ii) Otherwise, Case:” and promote all the subrules of ii) one level of nesting.


ed SR 20) concerning row pattern recognition is an interloper between SR 19) and SR 21) which are both about updatability. Actually, SR 21) can be deduced from SR 19)a)

Delete SR 21):

21) A <data change delta table> is not generally updatable, not simply updatable, not effectively updatable, and not insertable-into.

US P02-07.07, <joined table>

te Currently, the so-called “common columns” that arise during the evaluation of a <natural join> or a <named join> are assumed to be not associated with (and hence not prefixable by) a range variable. Moreover, there is no syntax for associating an explicit range variable for such columns. This is not very user-friendly in that some of the query formulations that appear to be syntactically valid are declared as syntax errors. To protect against such errors, users are forced into writing complex query formulations. A better solution would be to provide additional syntax that would let the users associate a





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


range variable for the common columns.

US P02-07.07, <joined table>

te The evaluation of a FULL outer join in GR 5)d) requires XNA, which is defined in GR 3)d), but GR 3)d) is not executed for FULL outer joins.


US P02-07.09, <row pattern common syntax>

te It is not convenient to define a condition that requires universal quantification over rows mapped to a row pattern variable. For example, given a pattern such as PATTERN (X+ Y), it is not convenient to define Y with a condition that means “for all rows mapped to X, Y.C <> X.C”. The most obvious attempt would be

DEFINE Y AS X.C <> Y.C.

However, this fails because X.C only references the last row mapped to X. Next one might attempt to get a universal quantifier by using the boolean EVERY aggregate (if available, most implementations do not support EVERY), like this:

DEFINE Y AS EVERY (X.C <> Y.C)

but this is a syntax error because all row pattern variables in an aggregate must be the same. The condition can be expressed by using collection types, for example,

DEFINE Y AS Y.C NOT MEMBER OF COLLECT (X.C).





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


However, collection types are not widely supported.


te See articles by Barzan Mozafari et.al. in SIGMOD 2010 “K*SQL” and VLDB 2010 “From regular expressions to nested words”, which propose that complex patterns might be labeled, for example PATTERN (Z: A B+)*. In this example Z is a label for the complex pattern (A B+). Labels can then be used to qualify row pattern variables, referencing different iterations of the labeled pattern. For example, suppose a sequence of rows is to be matched to A B B A B B using this pattern. With current functionality, there is no way to distinguish a row mapped to B in the first set (rows 2 and 3) from a row mapped to B in the second set (rows 5 and 6). With the group label Z, Z.B can be used to reference rows in the current sequence of maps to B, whereas some function, say PRIOR(Z).B, might be used to reference rows in the prior set mapped to B. Mozafari’s papers show how labels can be used to define interesting patterns not currently expressible in SQL/RPR, such as the following “wedge” pattern: Find those stocks whose price fluctuates as a series of ‘V-shape’ patterns, where in each ‘V’ the range of the fluctuation becomes smaller, and eventually, the price rises up to higher than its starting point.



te The DEFINE clause defines row pattern variables using running semantics. This makes it difficult to express a pattern that requires final semantics on the pattern as a whole. For example, consider

PATTERN ( (A | B){10,10})

and suppose that one wants to insure that the final match has exactly 4 instances of A and 6 instances of B. The





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


condition

COUNT(A.*) = 4 AND COUNT(B.*) = 6

cannot be imposed on either A or B since the condition won’t be fulfilled until the last row. A workaround is to use

PATTERN ( (A|B){10,10} {- C -} )

and impose the condition in the definition of C (the exclusion syntax {- C -} is used since the user is not actually interested in row C). However, this means that a match cannot be found at the very end of the partition since there must be one additional row to map to C. The workaround is to add a dummy row to the end of the partition. However, the user should not have to go through such artificial devices to express this.

US P02-07.14, <window clause>

ed GR 5) defines the full window frame. GR 5)a) handles the case if there is no window framing clause; 5)b) handles if there is a window framing clause. The first three subrules within 5)b) are mutually exclusive (because <window frame units ::= RANGE | ROWS | GROUPS), but GR 5)b)iv) concerning <window frame exclusion> is orthogonal to the choice RANGE | ROWS | GROUPS. Thus the first three subrules of GR 5)b) look like a Case, but they cannot be because <window frame exclusion> is not orthogonal. The Case-like nature of subrules i) through iii) could be made into a genuine Case by subordinating all of them one level deeper. On the other hand, these rules have very deep nesting within





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


them as it is.


ed GR 3) talks of “window partitioning column”. However, SR 4) defines “partitioning column”. Most uses of “partition” in this subclause are qualified as “window partition”. It might be good to adhere to this convention throughout the subclause, and others that might refer to window partitioning.



ed GR 6)b) says to “let WF(R) denote the window frame of R as computed by the preceding rules”. However, the “preceding rules” must mean GR 5), which defines the “full window frame”.



ed GR 5)b)i)1) has a probable typo “computer value” instead of “computed value”

Edit the rule as follows:

In the following subrules, when performing addition or subtraction to combine a datetime and a year-month interval, if the result would raise the exception condition data exception — datetime field overflow because the <primary datetime field> DAY is not valid for the computer computed value of the <primary datetime field>s YEAR and MONTH, then the <primary datetime field> DAY is set to the last day that is valid for the <primary datetime field>s YEAR and MONTH, and no exception condition is raised.

US P02-07.15, <query specification>

te the definition of insertable-into joins is not realistic in practice, because it is dissimilar to the definition for updatable and deletable joins. With an equijoin, one rarely makes two columns for the equijoined value. The rules in 15.11 "Effect of inserting a table into a derived table" GR 2)b)iii)2) do not provide for setting both columns in the candidate rows to the same value. The rules for updatable and deletable joins only rarely make





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


more than one underlying table

updatable/deletable. It would be better if the definition of insertable-into join adopted the same policy.

US P02-07.16, <query expression>

te SR 30)d)i)4) states explicitly that a common column name is regarded as fully qualified. The preceding rule SR 30)d)i)3) also talks about fully qualified column names, but does not say what to do about common column names.

Edit 30)d)i)3) as follows:

3) Let SL be the <select list> of QS. Let SLT be obtained from SL by replacing each <column reference> with its fully qualified equivalent; in the case of common column names, each common column name is regarded as fully qualified.


te GR 5)b) and the informative note 288 tht follows it assume that there is a one-to-one relationship between the result of QE and the sort table of QE. This depends on some kind of magic such as a notion of row identity. Perhaps the transformation from the sort table of QE to the result of QE by discarding columns as described in note 288 can be moved into an actual GR.



te According to SR 4), T is a table. The value of T is computed in the GRs. Normally we do not declare variables for tables in SRs; perhaps SR 4) can be moved to the GRs. In addition, perhaps the rules can be rewritten to clarify that T is computed over the course of the GRs (some of the rows in T can be replaced during the GRs).



ed SR 3)j)ii)2)D)I) is structurally "P or Q and R" which is ambiguous because English conjunctions do not have a commonly agreed precedence. The rule says: "QS immediately contains a <select list> SL or TE immediately contains a <having clause> HC and SL or TE contain a <set function specification>."





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


US P02-08.02, <comparison predicate>

ed See minor editorial improvements to GR 1)b)ii) suggested below

Edit the lead paragraph of GR 1)b)ii) as follows:

ii) If the declared types of XV and YV are array types or distinct types whose source types are array types and the cardinalities of XV and YV are N1 and N2, respectively, then let Xi, 1 (one) ≤ i ≤ N1, denote a <value expression> whose value and declared type is that of the i-th element of XV and let Yi , 1 (one) ≤ i ≤ N2, denote a <value expression> whose value and declared type is that of the i-th element of YV. ...

Edit GR 1)b)ii)3) as follows:

3) X = Y is False if and only if one of the following is true:

A) N1 ≠ N2 or

B) N1 = N2 and for some i, 1 (one) ≤ i ≤ N1, NOT (Xi = Yi) is True, for some i.

US P02-09.16, Execution of array-returning functions

te The rules require that the call type data item is initially -1 (see especially GR 9)). This initialization is indeed made in 10.4 <routine invocation> (search for “call type data item” to find it), but it might be clearer to the reader if the initialization occurred in this subclause.


US P02-09.16, Execution of array-returning

te The size of the resulting array is not always specified. The two subclauses that invoke this subclause merely create an array AR without stipulating its size. This subclause uses the variable E to keep track of which





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


functions subscript to insert the next array element into. If there is no data on the open call, then AR is set to null; if there is no data on the first fetch call, then the size of AR is set to 0 elements, but otherwise the size of the output array is not set.

US P02-09.16, Execution of array-returning functions

te GR 11) begins “The following steps are applied as long as the call type data item has a value 0 (zero)…” and subrule d)i)3) begins “If the call type data item is 0 (zero), then…”. It would seem that the condition in subrule d)i)3) is trivially satisfied, and this condition is not needed..

Delete the phrase from GR 11)d)i)3):

3) If the call type data item is 0 (zero), then

Case:

US P02-09.30, Determination of view component privileges

te GR 4)b)i)1) is a Case. Beneath this case, the first subrule considers a <table reference> TR that is a <table name>. Then the second subrule claims that the only other case to consider is a <query name>. But surely there are other cases. Because GR 4)a) has limited GR 4)b) to just updatable <query specification>s, we do not need to worry about the non-updatable kinds of <table reference> such as <collection derived table>, <table function derived table>, or <data change delta table>. But what about <only spec> and <parenthesized join table>? See SXF-020 section 1.5.


US P02-09.30, Determination of view component privileges

te GR 4)b)i)2) creates a view component privilege descriptor for the single-table DELETE case, but does not note if it is immediately dependent on any privilege.

Contrast this with GR 4)b)i)3) subrules A) and B) which handle single-table UPDATE and INSERT and handle immediate dependencies, and with GR 4)b)ii)1) which handles the multi-table DELETE case, and handles immediate dependencies. The rules are due to SIA-018.


US P02-10.04, <routine invocation>

te Currently default values are only supported for IN parameters of SQL-invoked procedures. However, this





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


concept should be extended to INOUT parameters in a reasonable way as well.


te Currently default values are only supported for IN parameters of SQL-invoked procedures. This concept should be extended to parameters of SQL-invoked functions as well.



te Currently named arguments are only supported for SQL-invoked procedures (i.e., within a call statement). This concept should be extended to SQL-invoked functions as well.



te According to Framework 6.3.3.8 “General Rules not terminated on exception conditions”, the GRs of this Subclause are not terminated on an exception. We should scrutinize whether that is completely true. If it is true, it would be helpful to note that fact as the first GR. If it is only partially true, we might isolate the pseudocode that does not terminate on an exception in its own subclause, with a first GR noting that the subclause does not terminate on exceptions.

Similar remarks apply to 13.4 <SQL procedure statement>, 15.19 “Execution of triggers”, and 22.1 <direct SQL statement>.



te GR 8)b)i)1)M) says the the initial value of the save area data item when invoking an array-returning or multiset-returning external function is 0. But 11.60 <SQL-invoked routine> SR 20)d)iii)8)A) says its data type is character string. The GRs of 9.16 “Execution of array-returning functions" are no help; they just say that the value on each call is copied from the value on the previous call. (Perhaps this parameter is available to the user-defined





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


function for saving context.)


te It is not clear how SR1) and GR 1) work if the <routine invocation> is a <value expression primary>.


US P02-10.05, <character set specification>

te SR 2) describes the creation of a privilege, something we normally find in a GR. Moving this rule to this subclause’s GRs would not be correct because the premise is that the privilege has already been created before this subclause is invoked. Perhaps this rule belongs in Concepts since this privilege is essentially a configuration issue.


US P02-11.07, <unique constraint definition>

te SR 7) says “If the <unique specification> specifies PRIMARY KEY, then for each <column name> in the explicit or implicit <unique column list> for which NOT NULL is not specified, NOT NULL is implicit in the <column definition>.” That’s fine if the <unique constraint definition> is contained in a <table definition>, but if it is contained in an ALTER TABLE statement there is no <column definition>. Also, defining a separate NOT NULL constraint on each primary key column seems to be unnecessary in view of SR 5)e)i).


US P02-11.16, <drop column not null clause>

te The GRs do not say what to do if the column is part of a primary key.


US P02-11.26, <drop table constraint definition>

te An identity column has an implicit NOT NULL constraint (11.4 <column definition> SR 16)d)) yet there is no RESTRICT or CASCADE rule about what happens to the identity column if this constraint is dropped.


US P02-11.32, <view definition>

te SR 21)s)ii)2) says that for a referenceable view whose reference type has a derived representation, the basis table shall have a candidate key that is a subset of the underlying columns of the attributes of the derived





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


representation. This does not prevent the following scenario: basis table has candidate key (A, B) and the expression defining a column corresponding to an attribute of the derived representation is A+B. Even though the key (A, B) is unique, the value A+B is not unique, so this condition is not enough to insure that derived representations are unique, as required in 4.15.9 “Referenceable tables, subtables and supertables” penultimate paragraph.


te Regarding referenceable base tables, 11.3 <table definition> SR 11)g)i) allows <scope clause> for originally-defined columns but not for inherited columns.

11.32 <view definition> SR 21)u) does not have a similar restriction. Prior to KMG-033 section 6.16 instruction 6, the GRs of <view definition> did not create column descriptors for inherited columns. Thus prior to KMG-033, the user could specify a SCOPE clause for an inherited column of a referenceable view, but nothing was done with the information. After KMG-033, the SCOPE clause is actually saved in a column descriptor. While it is correct to create column descriptors for inherited columns, it is probably not correct to allow the user to specify a SCOPE for inherited columns, since this is a variance from the

practice with referenceable base tables.



te GR 1)h) sets updatability in column descriptors, but there are no rules setting the indications of insertable-into or updatable in the view’s table descriptors.



te GR 3) lead paragraph begins a loop over all underlying tables and all columns of a view. Subrule a) only needs the loop over underlying tables, and subrules b)i) and b)ii) each initiate another loop over all columns of V. Perhaps





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


the loop over all columns in the lead paragraph of GR 3) can be deleted.

US P02-11.49, <trigger definition>

te SR 15)d) says that you cannot define an INSTEAD OF trigger on a leaf underlying table of a view that specifies WITH CASCADED CHECK OPTION. But does this recurse deep enough? Don't we want to prohibit it on a view that is a generally underlying table of a view WITH CASCADED CHECK OPTION?



te INSTEAD OF trigger on a view V should be prohibited if there is a schema object dependent on V that performs a <data change delta table> that specifies FINAL TABLE that targets V, since the FINAL TABLE becomes illegal if the INSTEAD OF trigger is defined. SQL routines and triggered actions are two such categories of schema objects.



te SR 7)f) defines the scope of the old and new transition table and variable names to be <triggered action>. This means that they are not in scope in the <triggered when clause>. But in that case there is no way to evaluate the <search condition> in the <triggered when clause>, as required by 15.19 “Execution of triggers” GR 4)b)i).


US P02-11.60, <SQL-invoked routine>

te To meet the increasing demands for complex user-defined analytical functions required by the so-called Big Data applications, SQL-invoked functions need to be extended to handle tables as arguments and return tables as results. Moreover, such functions need to allow “generic” tables as input and output, i.e., tables whose definition (number of columns and their data types) is not known at the time of function creation but determined at the time of function invocation.


US P02-11.60, <SQL-

te SR 20)g) checks that the <data type> of an effective parameter is supported by the host language of an





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


invoked routine>

external SQL-invoked routine. In the case of an SQL-invoked function with PARAMETER STYLE SQL, the return type is converted into an OUT parameter in the effective parameter list by SR 20)d)iii)2) so the return type is checked against the supported types of the host language. However, for an external SQL-invoked routine with PARAMETER STYLE GENERAL, the return type is never checked against the supported types of the host language.

US P02-11.60, <SQL-invoked routine>

te SR 6)n)i) says “A <result cast from type> is specified that simply contains an <array type> or a <path-resolved user-defined type name> whose source type is an array type and does not contain a <locator indication>.” This is ambiguous because the English conjunctions “and” and “or” do not have commonly understood precedence. SR 6)n)ii), 6)o)i) and 6)o)ii) have the same problem.


US P02-12.01, <grant statement>

te GR 4)e) contains a case with two subrules i) and ii) but no “otherwise”. This means that there are cases in which WGO is not defined. Perhaps the REFERENCES privilege should not be granted if neither i) nor ii) applies.


US P02-12.02, <grant privilege statement>

te GR 7), 8) and 9) use <action> in a sloppy fashion. Elsewhere it is clear that an <action> with a <column name list> such as SELECT (C1) is not the same as an <action> without a <column name list> such as vanilla SELECT. What these rules intend to do is construct, e.g., SELECT (C1) as an <action> from the different <action> of SELECT, rather than use “the identical <action>”. We should also check other places that construct column or table/method privileges from table privileges.


US P02-12.07, <revoke statement>

te GR 5)a) uses the view privilege dependency descriptors to determine the direct dependencies of DML privileges on views. The dependency descriptors are created in 9.29 "Determination of view privileges" and 9.30





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


"Determination of view component privileges". However, those subclauses only compute the privileges of a view based on its view definition and result in view privileges with the special grantor _SYSTEM. This works for the definer of the view but not for anyone who is subsequently granted access to the view..

US P02-14.12, <merge statement>

te GR 6)a)i)1) assumes that the range variable for the target table is a <table name>, ignoring the fact that the BNF and Syntax Rules permit a correlation name.



te GR 6) lead paragraph appears to specify a loop over all <merge when clause>s. However, the subrules do not adhere to this strictly. In particular:

GR 6)a) appears to handle a single <merge when matched clause>. Its subrule ii) identifies a set of rows as the old delta table of merge operation. However, the old delta table must be the union across all <merge when matched clause>s, so it should not be subordinate to processing a single <merge when matched clause>.

GR 6)b) appears to handle a single <merge when not matched clause>. Subrules i) through vii) can certainly only handle a single <merge when not matched clause>. However, subrule viii) needs to form the union of the candidate rows from each <merge when not matched clause>.

For both of these, it would be better to have an explicit loop to do the processing of individual <merge when matched clause>s or <merge when not matched clause>, followed by separate rules after the loops to perform the





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


unions.


te CR 1)a) talks of an underlying table that is broadly contained in a piece of syntax. What must be meant is an underlying table specification. This was not fixed by KRK-021; maybe there are similar rules with the same problem.



te GR 6)b)iv) assumes that a <table or query name> can be used as a correlation name. This is not true if the <table or query name> is a <table name>..


US P02-14.15, <set clause list>

ed GR 1) says “A <set clause> specifies one or more object columns and an update value.” But in fact, if there is more than one object column, then there is more than one update value.

Edit GR 1) as follows:

1) A <set clause> specifies one or more object columns and an equal number of update values. An object column is a column identified by an <object column> in the <set clause>. The An update value is the value specified by the an <update source> contained in the <set clause>.

US P02-15.12, Effect of inserting a table into a viewed table

te GR 3)a) handles INSTEAD OF INSERT triggers. There is no check for either CASCADED CHECK OPTION or LOCAL CHECK OPTION (unlike GR 3)b)). This is correct in the case CASCADED CHECK OPTION, but what about LOCAL CHECK OPTION? See 11.49 <trigger definition> SR 15)c). The paper that introduced this is URC-033. Note that section 1.1 PDF page 4 item 6 says “WITH CHECK OPTION must not have been specified for the view”. Possibly the paper meant to prohibit both kinds of CHECK OPTION. Or possibly it meant to prohibit CASCADED CHECK OPTION (the default) but forgot to include the rules to enforce the LOCAL CHECK OPTION. This is also an issue for 15.15 “Effect of





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


replacing some rows in a viewed table”.

US P02-15.13, Effect of replacing rows in base tables

te GR 8) is responsible for computing generated columns. In the generation expression, the table name is a range variable referencing the current row (see 11.3 <table definition> SR 16) and 11.10 <alter table statement> SR 3).) This is not clear in GR 8).


US P02-15.18, Execution of AFTER triggers

ed There is no Format, therefore there is no need for Syntax Rules. Subclause 13.4 <SQL procedure statement> GR 15)b) invokes the Syntax Rules of 15.18 “Execution of AFTER triggers”. This is unusual for a GR to invoke an SR. Inspecting 15.18, it seems that the SRs are merely the kind of initialization that we commonly do in GRs. Therefore the anomaly can be removed by transferring all of the SRs into the GRs, after which <SQL procedure statement> GR 15)b) only needs to invoke the GRs of 15.18. The subclause signature of 15.18 would also need to be edited.


US P02-20.01, Description of SQL descriptor areas

te SR 3) describes how LEVEL is used to indicate subordinate descriptor areas, but it does not state what the value of LEVEL is for a “top-level” SQL item descriptor. Presumably it is 0, based on the initialization in 20.2 <allocate descriptor statement> GR 3)b). It would be helpful to the reader to clarify this in 20.1 “Description of SQL descriptor areas”.


US P02-20.01, Description of SQL descriptor areas

ed SR 1) says “An SQL item descriptor area comprises the items specified in Table 24 … “. This is the first of many rules that use the word “item”, sometimes for “SQL item descriptor” and sometimes for an “item” within the SQL descriptor area or SQL item descriptor area. Perhaps we could choose more distinct terminology for these two uses. Note that 20.4 <get descriptor statement> GR 7) lead paragraph last sentence already uses “field” as a synonym for “item” in the second sense. However it





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


might be best to avoid “field” because of row types (see 20.1 SR 4)a)) and “element” for collection types (see SR 4)b)). Attributes of structured types are not described in descriptors, but it might be good to avoid that name conflict as well. Some other possible terms are “characteristic”, “component” , “constituent”, “facet”, or “member”.

US P02-20.02, <allocate descriptor statement>

te GR 2) last sentence says "The maximum number of SQL descriptor areas that can be allocated at one time is implementation-defined." However, <occurrences> does not specify the number of SQL descriptor areas, it specifies the number of SQL item descriptor areas (see GR 3)b)). Annex B says that both the maximum number of SQL descriptor areas and SQL item descriptor areas are implementation-defined.


US P02-20.06, <prepare statement>

te Most of the subrules of GR 5)a) that identify exact numeric data types with scale 0 use NUMERIC (MP, 0); however, a few use INTEGER and a few use NUMERIC (MP). It might be better if they all used the same data type.


US P02-21.03, <embedded SQL Ada program>

ed SR 6) “The reference type identified by the <referenced type> contained in the <reference type> contained in an <Ada REF variable> is called the referenced type of the reference." was not moved up (by KOA-030 section 6.2) with the definition of the host parameter type of <AdA REF variable>, unlike all other embedded languages. This is not a bug, just an inconsistency.


US P02-21.04, <embedded SQL C program>

te <C NCHAR variable> permits an optional <character set specification>. According to SR 4)b)i), this declaration corresponds to a <host parameter data type> that is NATIONAL CHARACTER with the user-specified character set. However, NATIONAL CHARACTER type does not permit the user to specify a character set. There





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


is a similar problem in embedded COBOL, but none of the other embedded languages. The problem is not found in SQL-92, it first occurred in Bindings:1999. KOA-030 rearranged the SRs but did not aggravate or alleviate the problem.

US P02-21.04, <embedded SQL C program>

te SR 7) says "Except for array specifications for character strings, a <C variable definition> shall specify a scalar type." It is not clear what this rule is trying to say. First, is the "scalar type" a scalar type of C or of SQL? It can't be the

latter because of <C array locator variable> and <C multiset locator variable>. So presumably this means a scalar C type. But then, what about <C BINARY variable> and <C REF variable>, which are transformed into array of char? And what about <C BLOB variable>, which is transformed into a struct? Maybe we can just delete this rule, if the BNF and the transformations already insure that the C declarations are correct.


US P02-Annex D, Deprecated features

te SIMILAR was deprecated in Foundation:2011. It is time to delete SIMILAR.


US P02-Annex E, incompatibilities

ed The title of this annex should be changed to “Incompatibilities with ISO/IEC 9075:2011” and all incompatibilities with SQL:2008 should be deleted.


US P02-No specific location

te Currently, using the <cast specification> is the only way to convert a TIMESTAMP value into a string representation and vice versa. However, the <cast specification> is limited in that it accepts exactly one input format and produces one output format. Thus, there is a need for additional expressions/functions in the standard that allow the user to specify the format of the result (if





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


transforming a timestamp to string) or the format of the input (if transforming a string to a timestamp). For example, all of the following could be valid string representations of the same timestamp (but just the first one is recognized by the SQL standard):

‘2009-03-13 23:05:00’

‘03-13-2009 11.05.00 PM’

‘13.03.2009-23.05.00’

A function that would convert any of the three alternatives above to a SQL TIMESTAMP value would take two input values: the string representing the timestamp and another string representing the format of the first input string. As an example,

TIMESTAMP_FORMAT(’13.3.2009-23.05.00’, ‘DD.MM.YYYY-HH24.MI.SS’)

will return a timestamp value equivalent to TIMESTAMP‘2009-03-13 23:05:00’.

Conversely,

VARCHAR_FORMAT(TIMESTAMP‘2009-03-13 23:05:00’, ‘MM/DD/YYYY-HH12.MI.SS A.M.’)

will return a string of the following form:

’03/13/2009-11.05.00 P.M.’


te Currently the standard supports two broad classes of numbers, exact numeric

and approximate numeric. The approximate numeric category corresponds to

what is commonly called “binary floating point types” in hardware, which represent numbers using an exponent





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


and a mantissa, both in binary. Such binary floating point values generally do not have an exact representation in decimal. Values of exact numeric types do have an exact representation in decimal, but they suffer from the fact that the range of values supported by these types is much smaller than the range supported by approximate numeric types. This is problematic for a large class of applications in areas such as financial, insurance, and accounting, which require exact representation in decimal for a much bigger range of values. To meet the needs of such applications, it would be useful to support decimal floating point types which also represent numbers using an exponent and a mantissa, where both exponent and mantissa are in decimal, giving the advantages of the large range afforded by an exponent, and the exact equivalence to a decimal value. Such type(s) can have implementation-defined exponent range and number of significant digits.


te The SQL Standard currently supports ordinary arrays and user-defined distinct types based on arrays. Both have in common that the size is pre-defined (or, better defined when the type is created) and the data type of the index is numeric. Contrast this with a so-called “associative array”, which is a data type used to represent a generalized array with no predefined cardinality.

The next edition of the SQL Standard should add support for associative arrays.

Associative arrays contain an ordered set of zero or more elements of the same data type, where each element is ordered by and can be referenced by an index value. The index values of associative arrays are unique, are of the same data type, and do not have to be contiguous. The index type can be either INTEGER or VARCHAR. To enhance usability and consumability of associative





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


arrays, the user provides a name when an associative array is created.

For example:

CREATE TYPE capitalsArray AS VARCHAR(12) ARRAY[VARCHAR(16)];

-- The element type is VARCHAR(12) and the type of the index values is VARCHAR(16).

DECLARE capitals capitalsArray;

SET capitals['British Columbia'] = 'Victoria';

SET capitals['Alberta'] = 'Edmonton';

SET capitals['Manitoba'] = 'Winnipeg';

SET capitals['Ontario'] = 'Toronto';

SET capitals['Nova Scotia'] = 'Halifax';

Similarly, the value of a certain array element can be retrieved as follows (assuming x is a variable of type VARCHAR:

SET x = capitals['Ontario'];

The values of x is then ‘Toronto’.


te Today, a given trigger is written specifically for one event (INSERT, UPDATE, or DELETE). There are situations,





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2


where the trigger logic for all three events (or at least two) is very similar. In such situations, it was beneficial, if a single trigger could cover all three (or at least more than one) event. The SQL standard should add support for such multiple-event triggers.


te It is often necessary to completely replace the definition of a schema object, especially during the initial development of an application. Currently, the only way to handle this requirement is to drop the schema object and then recreate it. In addition to being cumbersome, this “drop-and-recreate” option has some disadvantages in that users who had been granted privileges on the dropped object will lose those privileges, resulting in dropping of objects dependent on those privileges.. Some products offer a better option by extending the CREATE statement with an “OR REPLACE” clause that creates the object if the schema does not contain the object with the specified name and if the schema already contains the object with the specified name, replaces the definition of the object without impacting any of the users who had been granted privileges on that object. Note that careful consideration must be given to determine the list of objects for which such a redefinition is appropriate and the list of conditions that must be satisfied for the redefinition to be considered safe.



te JavaScript Object Notation (popularly known as JSON) [RFC4627] is becoming increasingly important in Web- and Cloud-based communities for exchanging data between Web-based applications. This has in turn led to the demands for storage, retrieval, querying, and manipulation of JSON data in the context of SQL It is important that SQL respond to these requirements by providing appropriate extensions for handling JSON data.





1 2 (3) 4 5 (6) (7)


No./Annex

(e.g. 3.1)


e/Note(e.g. Table

1)

Type of

com-ment

2



te All Possible Problems and Editor’s Notes must be satisfactorily resolved and all problems discovered during the course of the ballot resolution process must be satisfactorily resolved.




Documents

SubCommittee Namejtc1sc32.org/doc/N2351-2400/32N2353-summ_of_voting-N2311... · Web viewIn addition, a word “item” at the end of 5th sentence is not expected, since the referent