ISO/IEC 9075-4:1999/Cor 2:2003
(Corrigendum)Information technology — Database languages — SQL — Part 4: Persistent Stored Modules (SQL/PSM) — Technical Corrigendum 2
Information technology — Database languages — SQL — Part 4: Persistent Stored Modules (SQL/PSM) — Technical Corrigendum 2
Technologies de l'information — Langages de base de données — SQL — Partie 4: Modules stockés persistants (SQL/PSM) — Rectificatif technique 2
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-4:1999
TECHNICAL CORRIGENDUM 2
Published 2003-06-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Database languages — SQL —
Part 4:
Persistent Stored Modules (SQL/PSM)
TECHNICAL CORRIGENDUM 2
Technologies de l'information — Langages de base de données — SQL —
Partie 4: Modules stockés persistants (SQL/PSM)
RECTIFICATIF TECHNIQUE 2
Technical Corrigendum 2 to ISO/IEC 9075-4:1999 was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.
ISO/IEC 9075-4:1999/Cor. 2:2003 cancels and replaces ISO/IEC 9075-4:1999/Cor. 1:2000.
Statement of purpose for rationale:
A statement indicating the rationale for each change to ISO/IEC 9075 is included. This is to inform the users of
that standard as to the reason why it was judged necessary to change the original wording. In many cases the
reason is editorial or to clarify the wording; in some cases it is to correct an error or an omission in the original
wording.
Notes on numbering:
Where this Corrigendum introduces new Syntax, Access, General and Conformance Rules, the new rules have
been numbered as follows:
Rules inserted between, for example, Rules 7) and 8) are numbered 7.1), 7.2), etc. [or 7) a.1), 7) a.2), etc.]. Those
inserted before Rule 1) are numbered 0.1), 0.2), etc.
Where this Corrigendum introduces new Subclauses, the new subclauses have b een numbered as follows:
Subclauses inserted between, for example, Subclause 4.3.2 and 4.3.3 are numbered 4.3.2a, 4.3.2b, etc.
Those inserted before, for example, 4.3.1 are numbered 4.3.0, 4.3.0a, etc.
ICS 35.060 Ref. No. ISO/IEC 9075-4:1999/Cor.2:2003(E)
© ISO/IEC 2003 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
Contents
Page
3.3.1.1 Exceptions . . . . . . . . 3
3.3.1.2 Other terms . . . . . . . . 3
3.3.2.1 Clause, Subclause, and Table relationships . . . . . . 3
4.2 SQL-invoked routines . . . . . 4
4.7 Diagnostics areas . . . . . . 5
4.8 Cursors . . . . . . . 5
4.9 Condition handling . . . . . 5
4.10 SQ L-stateme nts . . . . . . . 6
4.10.1 SQL-statements classified by function . . . . 7
4.10.7 SQ L-stateme nt atomicity . . . . . 7
4.11 SQL-sessions . . . . . . . 8
5.1 an d . . . . . 8
6.2 . . . . . . 8
8.1 . . . . . 9
9.12 . . . . . 9
9.13 . . . . . 10
9.18 . . . . . 10
9.19 . . . . . 10
10.2 . . . . 10
11.1 Calls to an
11.2 . . . . . 11
11.1 Calls to an externally-invo ked procedure . . . . . 12
12.2 . . . . . 12
13.1 . . . . . 13
13.2 . . . . . 14
13.5 . . . . . 1 6
13.7 . . . . . . . 16
13.13 . . . . . . 17
15.1 . . . . . 1 8
16.1 . . . . . 18
16.2 . . . . . 19
16.3 . . . . . 20
17.2 MODULE_P RIVILEGES view . . . . . 21
17.4 MODULES view . . . . . 21
19.1 SQLSTATE . . . . . . . 22
Annex A SQL Co nformance Su mmary . . . . . 23
Annex E Incompatibilities with ISO/IEC 9075:1992 . . . . . 23
Annex F SQL Feature Taxonomy . . . . . 23
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
Information technology — Database languages — SQL —
Part 4:
Persistent Stored Modules (SQL/PSM)
TECHNICAL CORRIGENDUM 2
3.3.1.1 Exceptions
1. Rationale: Delete definition of an unused term.
Delete Subclause 3.3.1.1.
3.3.1.2 Other terms
1. Rationale: Delete what is moved to Part 2.
st nd rd
Replace the 1 , 2 and 3 paragraphs with:
Insert this paragraph An SQ L-stateme nt S1 may be said to be executed as a direct result of executing an
S2 if S2 contains S1.
3.3.2.1 Clause, Subclause, and Table relationships
1. Rationale: Correct the classification of SQL-statements.
Insert the following row into Table 1, "Clause, Subclause, and Table relationships":
Clause, Subclause, or Table in this part of Corre spond ing Cla use, Su bclaus e, or Ta ble Part containing
ISO/IEC 9075 from another part correspondence
Subclause 4.10.2a “Preparable and Subclause 4.6.5 Preparable and ISO/IEC 907 5-5
immediately executable SQL- immedia tely executa ble SQL -statements
statements”
2. Rationale: Correct cross reference.
Replace the following rows in Table 1, "Clause, Subclause, and Table relationships":
Clause, Subclause, or Table in this part of Corre spond ing Cla use, Su bclaus e, or Ta ble Part containing
ISO/IEC 9075 from another part corre spon denc e4.10 .7
“SQL-statement
atomicity”
Subclause 4.10.7 “SQL-statement (none) (none)
atomicity”
with:
Clause, Subclause, or Table in this part of Corre spond ing Cla use, Su bclaus e, or Ta ble Part containing
ISO/IEC 9075 from another part correspondence
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 3 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
Subclause 4.10.7 “SQL-statement Subclause 4.30.4 “SQL-statement ISO/IEC 907 5-2
atomicity” atomicity”
3. Rationale: Address requirement for multiple diagnostics areas
Insert the following row into Table 1, "Clause, Subclause, and Table relationships":
Clause, Subclause, or Table in this part of Corre spond ing Cla use, Su bclaus e, or Ta ble Part containing
ISO/IEC 9075 from another part correspondence
Subclause 4.11, “SQL-sessions” Subclause 4.34, “SQL-sessions” ISO/IEC 907 5-2
4. Rationale: Correct cross reference.
Replace the following rows in Table 1, "Clause, Subclause, and Table relationships":
Clause, Subclause, or Table in this part of Corre spond ing Cla use, Su bclaus e, or Ta ble Part containing
ISO/IEC 9075 from another part correspondence
Subclause 4.11.1, ‘‘Privileges’’ Subclau se 4.31, “B asic security m odel” ISO/IEC 907 5-2
Clause 11, “SQL-client module” Subclau se 13.1, “
definition>”
with:
Clause, Subclause, or Table in this part of Corre spond ing Cla use, Su bclaus e, or Ta ble Part containing
ISO/IEC 9075 from another part correspondence
Subclause 4.11.1, ‘‘Privileges’’ Subclause 4.31.2, ‘‘Privileges’’ ISO/IEC 907 5-2
Clause 11, “SQL-client module” Subclause 13, “SQL-client modules” ISO/IEC 907 5-2
4.2 SQL-invoked routines
1. Rationale: Correct the Part Merge instructions
nd
Replace the 2 paragraph with:
Replace 32nd paragraph An SQL-invoked routine has a routine SQ L-path, which is inh erited from its
containing SQL-server module or schema, the current SQL-session, or the containing SQL-client module.
rd
Replace the 3 paragraph with:
Insert in the 34th paragraph — If the SQL-invoked routine is not a schema-level routine, then the
server module name> of the SQL-server module that includes the SQL-invoked routine and the
name> of the schema that includes the SQL-server module.
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
4.7 Diagnostics areas
1. Rationale: Address requirement for multiple diagnostics areas
Replace the entire Subclause with:
Replace paragraph 8 The is used to obtain information from an occupied
condition area, referenced by its ordinal position within the specified diagnostics area. Normally, only the first
(i.e., current) area may be specified. However, if a handler is active, it is also possible to reference the second
(i.e., most recen tly stacked) a rea, in order to o btain informa tion about the condition tha t caused the handler to
become active.
Insert this paragraph Information about a completion or exception condition that causes a handler to be
activated is pla ced into on e or more c ondition are as of the first diag nostics area before any handler is
activated. T he diagno stics area stack is then push ed so that the h andler can access that in formation e ven wh ile
its own execution is causing the first diagnostics area to be modified.
Insert this paragraph The first diagnostics area is emptied during the execution of a .
Information is added to the first diagnostics area during the execution of a .
4.8 Cursors
1. Rationale: Fix bug in processing results sets in PSM.
st
Replace the 1 paragraph with:
Insert this paragraph For every in a , a cursor is effectively created
each time the is executed, and destroyed when that execution completes, unless the
cursor is an open result set cursor.
4.9 Condition handling
1. Rationale: Address requirement for multiple diagnostics areas
th
Replace the 5 paragraph with:
A condition represents an error or informational state caused by execution of an .
Conditions are raised to prov ide information in a diagnostics area about the execution of an
statement>.
2. Rationale: Address requirement for multiple diagnostics areas. Simplify and clarify where execution
resumes.
th th th
Replace the 12 , 13 and 14 paragraphs, including NOTE 2, with:
If a handler typ e specifies C ONT INUE , then, whe n the hand ler is activated, it w ill:
— Push the diagnostics area stack.
— Execute the handler action.
© ISO/IEC 2003 – All rights reserved 5
---------------------- Page: 5 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
— Pop the diagnostics area stack.
— Cause the SQL-session to continue as it would have done if execution of the innermost executing
statement that raised the condition had completed.
If a handler typ e specifies E XIT, then , when the handler is activ ated, it will:
— Push the diagnostics area stack.
— Execute the handler action.
— Pop the diagnostics area stack.
— Implicitly LEAVE the for which the handler was created, with no active
exception condition.
If a handler typ e specifies U NDO , then, whe n the hand ler is activated, it w ill:
— Push the diagnostics area stack.
— Roll back all of the changes to SQL-data or to schemas by the execution of every SQL-statement
contained in the SQL-statement list of the at the scope of the handler and
cancel any s triggered by the execution of such statements.
— Execute the handler action.
— Pop the diagnostics area stack.
— Cause th e SQL-s ession to co ntinue as it w ould have done if exe cution of the
for which the handler was created had completed.
4.10 SQL-statements
1. Rationale: Correct the classification of SQL-statements.
Insert the following Subclause after Subclause 4.10.2, “Embeddable SQL-statements”:
4.10.2a Preparable and immediately executable SQL-statements
Insert this paragraph Consequently, the following SQL-control statements are not preparable:
—
—
—
—
—
6 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
—
—
—
—
—
Insert this paragraph Consequently, the following SQL-control declarations are not preparable:
—
—
—
4.10.1 SQL-statements classified by function
1. Rationale: Correct the classification of SQL-statements.
nd nd
Delete the 2 bullet from the 2 paragraph.
4.10.7 SQL-statement atomicity
1. Rationale: Not all SQL-statements are atomic.
Insert the following paragraph:
Insert this paragraph The following are non-atomic SQL-statements:
—
— , unless BEGIN ATOMIC is specified
—
—
—
—
—
—
© ISO/IEC 2003 – All rights reserved 7
---------------------- Page: 7 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
4.11 SQL-sessions
1. Rationale: Address requirement for multiple diagnostics areas
Insert the following Subclause:
4.11 SQL-sessions
Insert this paragraph Certain operations during an SQL-session SS are possible only when SS is in condition
handling mode. This mode becomes in effect when execution of an SQL-statement has completed to the extent
that all diagnostics information pertaining to that execution is recorded in the first diagnostics area. Condition
handling mode ceases to be in effect when execution of the next SQL-statement begins.
5.1 and
1. Rationale: Editorial - Correct reserved and non-reserved word lists.
In the Format, in the production for delete the alternatives:
| REDO
6.2
1. Rationale: Correct definition of possible scope tags. Adjust rule numbering to accommodate changes in Part
2.
Replace Syntax Rule 2) with:
2) Replace SR7)a)ii) Otherwise IC shall be con tained with in the scope of one or m ore expos ed
or query name> s or s whose associated tables include a column whose
is equivalent to I or within the scope of a whose associated
1
declaration list> includes an SQL parameter whose is equivalent to I or within the scope
1
of one or m ore s who se associate d inc ludes an S QL varia ble
whose is equivalent to I . Let the phrase possible scope tags denote tho se expose d
1
or query name>s, s, s and s.
Replace Syntax Rule 3) with:
3) Insert after SR7)a)ii)1)B) If IPST is a , th en let SV be the SQL variable whose
is equivalent to I . PIC is the basis of IC, the basis length is 1 (one), the basis scope is the
1 1
scope of SP, and the basis referent is SV.
8 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
8.1
1. Rationale: The formulation “ of an SQL parameter of an SQL-invoked routine”
remains due to historical reasons and is a synonym to , which is now used in the
BNF definition of .
Replace Syntax Rule 6) with:
6) Replace SR8)c)i)4)B) If A is an , an or a
i
, then P shall be assignable to A , according to the Syntax Rules of Subclause 9.2,
i i
"Store assignment", in ISO/IEC 9075-2, with A and P as TARGET and VALUE, respectively.
i i
NOTE 6.1 — The can only be a new transition column reference.
2. Rationale: Genera l Rule 3) cove rs the case o f specifying an , so Genera l Rule 2) is
redundant. Correct tagging in General Rule 3). The formulation “ of an SQL
parameter of an SQL-invoked routine” remains due to historical reasons and is a synonym to
parameter reference>, which is now used in the BNF definition of .
Delete Genera l Rule 2).
Replace General Rule 3) with:
3) Replace GR10)b)ii) If TS is an , an , or a
i
, then CPV is assigned to TS according to the rules of Sub clause 9.2, "Store
i i
assignment", in ISO/IEC 9075-2.
NOTE 7.1 — The can only be a new transition column reference.
9.12
1. Rationale: Standardise terminology.
Replace the Function with:
Destroy a collation.
2. Rationale: Add missing rule.
Insert the following Syntax Rule:
1) Insert after SR4 If RESTRICT is specified, then C shall not be referenced in the module descriptor of
any SQL-server module.
© ISO/IEC 2003 – All rights reserved 9
---------------------- Page: 9 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
9.13
1. Rationale: Add missing rule.
Insert the following Syntax Rule:
1) Insert after SR5 If RESTRICT is specified, then C shall not be referenced in the module descriptor
of any SQL-server module.
9.18
1. Rationale: Editorial.
In the Format, replace the production with:
::=
CREATE MODULE
[ ]
[ ]
[ ]
[ . ]
.
END MODULE
9.19
1. Rationale: Remove redundant and confusing references to assertion descriptor.
Replace Syntax Rule 3) c) as follows:
3) c) The of any cons traint descriptor.
10.2
1. Rationale: There is no immediately contained in a .
Replace Syntax Rule 6) f) with:
6) f) SELECT privileges on every and contained in a
expression> simply contained in an contained in the of any
SQL-invoked routine included in SSM.
2. Rationale: Correct the rules for dependency on USAGE privilege for a user-defined type.
Replace Syntax Rule 6) j) with:
6) j) USAGE privilege on every domain, every collation, every character set, and every transliteration
whose name is contained in the of any SQL-invoked routine included in SSM.
j.1) USAGE privilege on every user-defined type UDT such that there is a contained in the
10 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
of any SQL-invoked routine included in SSM that is usage-dependent on UDT.
3. Rationale: Replace usage of undefined tag RD.
Replace Syntax Rules 6) l), m) and n) with:
6) l) SELECT privilege WITH HIERARC HY OPTION on at least one supertable of the scoped
table of any that is containe d in any co ntained in
the of any SQL-invoked routine included in SSM.
m) SELECT privilege WITH HIERARC HY OPTION on at least one supertable of the scoped
table of any that is containe d in any or < select list>
immediately contained in a contained in the
body> of any SQL-invoked included in SSM.
n) SELECT privilege WITH HIERARC HY OPTION on at least one supertable of the scoped
table of any that is contained in any contained in a
, an , o r a
contained in the of any SQL-invoked routine included in SSM.
4. Rationale: Replace u sage of un defined tag RD and there is no < row valu e express ion> imm ediately
contained in a .
Replace Syntax Rule 6) o) with:
6) o) SELECT privilege WITH HIERARC HY OPTION on at least one supertable of the scoped table of
any that is contained in any simply contained in an
contained in the of any SQL-invoked included in SSM.
11.1 Calls to an
1. Rationale: Address requirement for multiple diagnostics areas
In Syntax Rule 1) add the following text to the package definition for SQLSTATE_CODES:
DIAGNOSTICS_EXCEPTION_STACKED_DIAGNOSTICS_AREA_ACCESSED_WHEN_NO_HANDLER_ACTIVE:
constant SQLSTATE_TYPE := "0Z002"
11.2
1. Rationale: Address requirement for multiple diagnostics areas
Insert the following General Rules:
1) Replace GR5)a)iii)6) If S is not a , then the first diagnostics area is emptied.
2) Insert after GR7) Condition handling mode becomes in effect in the SQL-session.
3) Insert after GR7) The General Rules of Subclause 13.2, "", are applied.
4) Insert this rule Condition handling mode ceases to be in effect in the SQL-session.
© ISO/IEC 2003 – All rights reserved 11
---------------------- Page: 11 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
2. Rationale: Editorial - to correct reference.
Replace Conformance Rule 1) with:
1) Without Feature P001, “Stored modules”, an shall not be an
module definition> or a .
11.1 Calls to an externally-invoked procedure
1. Rationale: Remove undefined constants.
Replace Syntax Rules 1) with:
1) Replace SR2)e)
CASE_NOT_FOUND_FOR_CASE_STATEMENT_NO_SUBCLASS:
constant SQLSTATE_TYPE :="20000";
DATA_EXCEPTION_NULL_VALUE_IN_FIELD_REFERENCE:
constant SQLSTATE_TYPE :="22006";
RESIGNAL_WHEN_HANDLER_NOT_ACTIVE_NO_SUBCLASS:
constant SQLSTATE_TYPE :="0K000";
UNHANDLED_USER_DEFINED_EXCEPTION_NO_SUBCLASS:
constant SQLSTATE_TYPE :="45000";
12.2
1. Rationale: Replace m isleading tex t.
Replace Syntax Rules 2) and 3) with:
2) Replace SR6)a)i) If TS is an or an , then the
Syntax Rules of Subclause 9.2, "Store assignment", in ISO/IEC 9072-2, apply to TS and the row type
of table T as TARGET and VALUE, respectively.
3) Replace SR6)b)ii) For each TS1 that is an or an
, the Syntax Rules of Subclause 9.2, "Store assignment", in ISO/IEC 9072-
2, apply to TS1 and the corresponding column of table T as TARGET and VALUE, respectively.
Replace General Rules 1) with:
1) Replace GR7)a)i) If TS is an or an , then the
General Rules of Subclause 9.2, "Store assignment", in ISO/IEC 9072-2, apply to TS and the current
row as TARGET and VALUE, respectively.
2. Rationale: Replace m isleading tex t and corre ct symbo l .
Replace General Rule 2) with:
2) Replace GR7)b)i) If TV is an or an , then the
General Rules of Subclause 9.2, "Store assignment", in ISO/IEC 9072-2, apply to TV and SV as
TARGET and VALUE, respectively.
12 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
13.1
1. Rationale: Remove confusion of duplicate tags.
Replace Syntax Rule 8) with:
8) Let CON be the immediately contained in a contained in a
. The declared local name of the is CON.
2. Rationale: Editorial.
Replace General Rule 3) b) with:
3) b) The General Rules of Subclause 13.5, "", in ISO 9075-2, are evaluated
with S as the executing statement.
i
3. Rationale: Correct editorial error.
Replace General Rule 3) c) with:
3) c) If the execution of S terminates with exception conditions, then:
i
i) The follow ing is effectively e xecuted w ithout further S yntax Ru le
checking:
RESIGNAL
ii) If there are unhandled exception conditions or completion conditions other than successful
completion at the completion of the execu tion of a handler (if any), then the execu tion of CS is
terminated immediately.
1) For every open c ursor CR that is declared in the of CS, the
following SQL-statement is effectively executed:
CLOSE CR
2) The SQL variables, cursors, and handlers specified in the , the
, and the < local handler declaration list> of CS are destroyed.
4. Rationale: Fix bug in processing results sets in PSM.
Replace General Rule 4) with:
4) For every open c ursor CR that is not a result set cursor that is declared in the
list> of CS, the following SQL-statement is effectively executed:
CLOSE CR
NOTE 16.1 — Result set cursor is defined in Subclause 4.29, Cursors in ISO/IEC 9075-2.
Replace General Rule 5) with:
© ISO/IEC 2003 – All rights reserved 13
---------------------- Page: 13 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
5) The SQL variables, cursors that are not open result set cursors, and handlers specified in
declaration list>, the , and the of CS are
destroyed.
13.2
1. Rationale: Simplify and clarify where execution resumes.
Replace General Rule 2) with:
2) Let CS be the simply containing HD.
2. Rationale: Fix bug in processing results sets in PSM, simplify and clarify where execution resumes and
address th e requirem ent for mu ltiple diagnos tics areas.
Replace General Rule 3) with:
3) When H is activated,
Case:
a) If HD specifies CONTINUE, then:
i) The General Rules of Subclause 22.2, "Pushing and popping diagnostics areas" are applied,
with PUSH as OPERATION and the diagnostics area stack as STACK.
ii) HA is executed.
iii) Case:
A) If there is an unhandled condition other than successful completion at the completion of
HA, then
I) The Gene ral Rules of Subclause 2 2.2, "Pushing and p opping diagnostics area s" are
applied, with PUSH as OPERATION and the diagnostics area stack as STACK.
II) The following is effectively executed:
RESIGNAL
B) Otherwise:
I) The Gene ral Rules of Subclause 2 2.2, "Pushing and p opping diagnostics area s" are
applied, with POP as OPERATION and the diagnostics area stack as STACK.
II) HA completes with completion condition successful completion and the SQL-session
continues as it would have done if execution of the innermost executing statement that
raised the condition had completed.
b) If HD specifies EXIT, then:
i) The General Rules of Subclause 22.2, "Pushing and popping diagnostics areas" are applied,
14 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/IEC 9075-4:1999/Cor.2:2003(E)
with PUSH as OPERATION and the diagnostics area stack as STACK.
ii) HA is executed.
iii) For every open c ursor CR that was declared in CS and that is not a result set cursor, the
following statement is implicitly executed:
CLOSE CR
NOTE 17.1 — Result set cursor is defined in Subclause 4.29, Cursors in ISO/IEC 9075-2.
iv) Case:
A) If there is an unhandled condition other than successful completion at the completion of
HA, then
I) The Gene ral Rules of Subclause 2 2.2, "Pushing and p opping diagnostics area s" are
applied, with PUSH as OPERATION and the diagnostics area stack as STACK.
II) The following is effectively executed:
RESIGNAL
B) Otherwise:
I) The Gene ral Rules of Subclause 2 2.2, "Pushing and p opping diagnostics area s" are
applied, with POP as OPERATION and the diagnostics area stack as STACK.
II) HA completes with completion condition successful completion and the SQL-session
continues as it would h ave done if execution o f CS had completed.
c) If HD specifies UNDO, then:
i) The General Rules of Subclause 22.2, "Pushing and popping diagnostics areas" are applied,
with PUSH as OPERATION and the diagnostics area stack as STACK.
ii) All chang es made to SQL-d ata or schem as by the ex ecution of S QL-statem ents contain ed in
the of CS and any s triggered
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.