ISO/IEC 9075-9:2001/Cor 1:2003
(Corrigendum)Information technology — Database languages — SQL — Part 9: Management of External Data (SQL/MED) — Technical Corrigendum 1
Information technology — Database languages — SQL — Part 9: Management of External Data (SQL/MED) — Technical Corrigendum 1
Technologies de l'information — Langages de base de données — SQL — Partie 9: Gestion des données externes (SQL/MED) — Rectificatif technique 1
General Information
Relations
Standards Content (Sample)
INTERNATIONAL STANDARD ISO/IEC 9075-9:2001
TECHNICAL CORRIGENDUM 1
Published 2003-06-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION
INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОМИССИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE
Information technology — Database languages — SQL —
Part 9:
Management of External Data (SQL/MED)
TECHNICAL CORRIGENDUM 1
Technologies de l'information — Langages de base de données — SQL —
Partie 9: Gestion des données externes (SQL/MED)
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to ISO/IEC 9075-9:2001 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 32, Data management and interchange.
Statement of purpose for rationale:
A statement indicating the rationale for each change to ISO/IEC 9075 is included. This is to inform the users of
that standard as to the reason why it was judged necessary to change the original wording. In many cases the
reason is editorial or to clarify the wording; in some cases it is to correct an error or an omission in the original
wording.
Notes on numbering:
Where this Corrigendum introduces new Syntax, Access, General and Conformance Rules, the new rules have
been numbered as follows:
Rules inserted between, for example, Rules 7) and 8) are numbered 7.1), 7.2), etc. [or 7) a.1), 7) a.2), etc.]. Those
inserted before Rule 1) are numbered 0.1), 0.2), etc.
Where this Corrigendum introduces new Subclauses, the new subclauses have 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-9:2001/Cor.1:2003(E)
© ISO/IEC 2003 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
Contents
Page
4.5 User mappings . . . . . . . . 3
4.8 Datalinks . . . . . . . . 3
4.9 Type conversions and mixing of data types . . . . . 4
4.18.1 Handles . . . . . . . 4
4.18.4 Return codes . . . . . . . 4
4.18.7 Foreign-data wrapper descriptor areas . . . . . 4
5.2 an d . . . . . 5
6.2 . . . . . 5
6.5 . . . . . . . 6
7.1 . . . . . . 6
13.1 . . . . . 7
13.4 . . . . . . . . . 8
14.1 . . . . . 8
14.3 . . . . . 9
18.4 . . . . . 9
18.6 . . . . . 9
22.9 Tables used with SQL/MED . . . . . 9
23.2 invocation . . . . . 10
23.3.1 AllocWrapperEnv . . . . . 10
23.3.3 ConnectServer . . . . . . 10
23.3.18 InitRequest . . . . . . . 10
23.3.20 Open . . . . . . . 11
23.3.22 TransmitRequest . . . . . 12
23.4.1 AllocDescriptor . . . . . 13
23.4.2 FreeDescriptor . . . . . . 13
23.4.4 GetDescriptor . . . . . . . 13
23.4.36 SetDescriptor . . . . . . 14
23.5.1 GetDiagnostics . . . . . . 16
25.1 ATTRIBUTES view . . . . . 16
25.2 COLUMN _OPTIONS view . . . . . 1 7
25.3 COLUMN S view . . . . . 1 7
25.4 FOREIGN_DAT A_WRA PPER_OPTIONS view . . . . . 1 8
25.5 FOREIGN_DAT A_WRA PPERS view . . . . . 18
25.6 FOREIGN_SERV ER_OPTIONS view . . . . . 1 9
25.7 FOREIGN_SERV ERS view . . . . . 19
25.10 USER_MAP_O PTIONS view . . . . . 20
25. 12 Sho rt name views . . . . 20
Annex B Implem entation-de fined eleme nts . . . . . 21
Annex C Implem entation-de penden t elements . . . . . 22
Annex E Incompatibilities with ISO/IEC 9075:1992 . . . . . 22
2 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
Information technology — Database languages — SQL —
Part 9:
Management of External Data (SQL/MED)
TECHNICAL CORRIGENDUM 1
4.5 User mappings
1. Rationale: Do not describe non-schema objects as being in a catalog.
nd
Replace the 2 paragraph with:
A user mapping is defined by invoking an . Invocation of an
definition> results in the creation of a user mapping descriptor in the SQL-environment. A user mapping
descriptor consists of:
— An authorization iden tifier.
— A foreign server nam e, identifying a foreign server descriptor.
— A generic options d escriptor.
4.8 Datalinks
1. Rationale: Clarify the sem antics of built-in functions.
Replace the 2nd paragraph with:
The File Reference of a datalink is accessible by invoking operators defined in this part of ISO/IEC 9075. The
character set of the File Reference, referred to as the datalink character set is implementation-defined.
Replace the 7th paragraph with:
With the function provided by datalinks and the datalinker, it is possible to specify that access to the files
should be mediated b y the SQ L-server rath er than by the external data manage r. When access to the files is
mediated by an SQL-server, any request to access a file must operate on an SQL-mediated datalink to obtain a
character strin g with w hich to referen ce the file, using one of the o perators pro vided for tha t purpose. T his
character string is constructed by combining the File Reference of a datalink value with an encrypted value
called an access token. The gene ration of the ac cess token and the m ethod of co mbining it w ith the File
Referenc e is implem entation-de penden t. When the application uses the retur ned chara cter string valu e to
access a file, the datalinker checks to see if the access token is valid. If it is valid, then the a pplication is
allowed to access the file pointed to by the File Reference. Every attempt by an application to access, without
a valid acce ss token, a file re ferenced b y an SQ L-mediate d datalink is u nsuccess ful. The time at which a valid
access token ceases to be valid is implementation-defined.
© ISO/IEC 2003 – All rights reserved 3
---------------------- Page: 3 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
2. Rationale: Clarify assignable and comparable.
th
Insert the following paragraph after the 7 paragraph:
Datalinks are not comparable. A datalink is assignable only to sites of type DATALINK.
4.9 Type conversions and mixing of data types
1. Rationale: Clarify assignable and comparable.
Delete the subclause.
4.18.1 Handles
1. Rationale: Editorial.
nd th
In the 2 paragraph, replace the 4 bullet with:
— Reque st handle : This hand le is allocated b y the SQL -server to refere nce an SQ L-stateme nt that is to
be executed by a foreign server. A request handle may reference a simple statement, such as SELECT
* FROM T, or it may refere nce a com plex stateme nt that include s predicates , joins, ordering , etc. A
request handle is used by the foreign-data wrapper to retrieve (for example) the names of foreign tables
referenced in the from cla use, the nam es of colum n reference s in the select list, etc, using foreign -data
wrapper interface SQL-server routines. This handle is allocated implicitly.
4.18.4 Return codes
1. Rationale: Add missing text for Success with Information condition.
st
paragraph as the seco nd bullet:
Insert the following into the 1
— A value of 1 (one) indicates Success with information. The foreign-data wrapper interface routine
executed successfu lly but a com pletion con dition was ra ised: warning.
4.18.7 Foreign-data wrapper descriptor areas
1. Rationale: Editorial - misspelled acronym.
nd th
Modify the 2 bullet of the 5 paragraph with:
— Wrap per Row Descripto r (WR D): This de scriptor is allocate d by the SQ L-server if a fo reign-data
wrapper requests its allocation. It is used to describe the result of a statement to be executed by that
foreign-data wrapper in pass-through mode, and is associated with an ExecutionHandle. The foreign-
data wrapper uses the SetDescriptor() routine to set information in the WRD. The SQL-server
can obtain the handle to a WRD by invoking the GetWRDHandle() routine. It can then retrieve the
information in that WRD by invoking the GetDescriptor() routine.
4 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
5.2 and
1. Rationale: Correct the BNF of and .
In the Format, replace the productions for and with:
::=
!! All alternatives from ISO/IEC 9075-2
| !!All alternatives from ISO/IEC 9075-5
| BLOCKED
| CONTROL
| DB
| FILE | FS
| INTEGRITY
| LIBRARY | LIMIT | LINK
| MAPPING
| PASSTHROUGH | PERMISSION
| RECOVERY | RESTORE
| SELECTIVE | SERVER
| UNLINK
| VERSION
| WRAPPER
| YES
::=
!! All alternatives from ISO/IEC 9075-2
| !!All alternatives from ISO/IEC 9075-5
| DATALINK | DLURLCOMPLETE | DLURLPATH | DLURLPATHONLY | DLURLSCHEME
| DLURLSERVER | DLVALUE
| IMPORT
6.2
1. Rationale: there is no immediately contained in a .
Replace Access Rule 1) with:
1) Replace AR 1) If CR is a whose qualifying table is a base table, a foreign table or
a viewed table and that is contained in any of:
— A simply contained in a , a or an
.
— A contained in a .
— A
1. Rationale: There is no immediately contained in a .
Replace Access Rule 1) b) with:
1) b) If T is a base table, a foreign table or a viewed table and the
of:
— A simply contained in a , a , or an
.
— A
— A imm ediately con tained in a < delete statem ent: searche d> or an < update
statement: searched>.
— A simply contained in an .
then
Case:
i) If
of the that owns the containing schema shall include SELECT on at
least one column of T.
ii) Otherwise, the current privilege s shall include SELE CT on at least one co lumn of T.
NOTE 29 — “applicable privileges” and “current privileges” are defined in Subclause 11.1, “”.
6 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
2. Rationale: Delete incorrect implication that there will only every be 1 TRH.
Replace General Rule 1) b) ix) with:
1) b) ix) Let TRDH be the TableRefe renceDescriptorH andle allocated for TRD.
3. Rationale: Clarify wh en a desc riptor hand le is used instea d of the desc riptor itself.
Replace General Rules 1) b) xvii) and 1) b) xviii) with:
1) b) xvii) Let NC be the value of the COUNT descriptor field that would be returned by invocation of
the GetDescriptor() routine with TRDH as the DescriptorHandle parameter, 0 (zero)
as the RecordNumber parameter, and the code for COUNT from Table 32, “Codes used for
foreign-data wrappe r descriptor fields”, as the FieldIdentifier parameter.
1) b) xviii) Let DT be the effective data type of the j-th column, for 1 (one) £ j £ NC, as represented by
j
the values of the TYPE, LENGTH, OCTET_LENGTH, PRECISION, SCALE,
DATETIME_INTERVAL_CODE, DATETIME_INTERVAL_PRECISON,
CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, USER_DEFINED_TYPE_CATALOG,
USER_DEFINED_TYPE_SCHEMA, USER_DEFINED_TYPE_NAME,
SCOPE_CAT ALOG, SCOPE _SCHEMA , and SCOPE_NAM E fields that would be
returned by separate invocations of the GetDescriptor() routine with TRDH as the
Descripto rHandle paramete r, j as the RecordNumber parameter, and the code for the fields
TYPE, LENGTH, OCTET_LENGTH, PRECISION, SCALE,
DATETIME_INTERVAL_CODE, DATETIME_INTERVAL_PRECISON,
CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA,
CHARACTER_SET_NAME, USER_DEFINED_TYPE_CATALOG,
USER_DEFINED_TYPE_SCHEMA, USER_DEFINED_TYPE_NAME
SCOPE_CAT ALOG, SCOPE _SCHEMA , and SCOPE_NAM E from Table 32 “Codes used
for foreign-data wrapper d escriptor fields”, as the FieldIdentifier parameter.
4. Rationale: Correct undefined tag.
Replace General Rule 1) b) xxvi) with:
1) b) xxvi) The
repeated invocation of the Iterate( ) routine in the library identified by WRLN
with EXH as the argument until the return code indicates No data found.
13.1
1. Rationale: Delete the optional AUTHORIZATION-clause from .
In the Format replace the production for with:
::=
CREATE SERVER
[ TYPE ]
[ VERSION ]
FOREIGN DATA WRAPPER
[ ]
© ISO/IEC 2003 – All rights reserved 7
---------------------- Page: 7 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
Delete Syntax R ule 3).
Replace General Rule 1) e) with:
1) e) The current authorization iden tifier.
Replace General Rule 2) with:
2) A privilege descriptor is created that defines the USAGE privilege on this foreign server to the current
authorization identifier. The grantor of the privilege descriptor is set to the special grantor value
‘‘_SYSTEM’’. This privilege is grantable.
13.4
1. Rationale: Delete the optional AUTHORIZATION-clause from .
In the Format replace the production for with:
::=
CREATE FOREIGN DATA WRAPPER
[ ]
[ ]
Delete Syntax R ule 3).
Replace General Rule 1) b) with:
1) b) The current authorization iden tifier.
Replace General Rule 2) with:
2) A privilege descriptor is created that defines the USAGE privilege on this foreign-data wrapper to the
current authorization identifier. The grantor of the privilege descriptor is set to the special grantor value
‘‘_SYSTEM’’. This privilege is grantable.
14.1
1. Rationale: Cater properly for abandoned foreign table descriptors.
Replace Syntax Rule 1) with:
1) Insert after SR 21) Let T be any foreign table descriptor included in S1. T is said to be abandoned if
the revoke destruction action would result in A1 no longer having USAGE privilege on the foreign
server associated with the foreign table described by T.
Replace Syntax Rule 3) with:
3) Augment SR 36) Add ab andone d foreign se rver descripto r, and aban doned fo reign table de scriptor to
the list of objects that shall not ex ist.
8 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
Insert the following General Rule:
2) Insert this GR For every aband oned foreign table descriptor FT, let FTN be the
The follow ing is effectively ex ecuted w ithout further A ccess Ru le
checking:
DROP FOREIGN TABLE S1.FTN CASCADE
14.3
1. Rationale: Correct s ymbol.
Replace General Rule 1) with:
1) The General Rules of Subclause 11.3, ‘‘’’, are applied to AGO with the ge neric
options descriptor included in UMD as the applicable generic option s descriptor.
18.4
1. Rationale: Clarify that wrapper row descriptor is meant by WRD.
Replace General Rule 1) a) with:
1) a) Let EXH be the Exe cutionH andle asso ciated with < SQL sta tement nam e>. Let WPD and WRD be
the wrapper parameter descriptor and wrapper row descriptor, respectively, associated with the
WPDHandle and W RDHandle, respectively, that would be returned by the invocation of the
GetWPDHandle() and GetWRDHandle() routines with EXH as the Exe cutionH andle
parameter.
18.6
1. Rationale: Clarify that wrapper row descriptor is meant by WRD, and server row descriptor by SRD.
Replace General Rule 1) c) with:
1) c) Let EXH be the ExecutionHandle associated with SN. Let WRD and SRD be the wrapper row
descriptor and server row descriptor, respectively, associated with the WRDH andle and
SRDHandle, respectively, that would be returned by the invocation of the GetWRDHandle() and
GetSRDHandle() routines with EXH as the ExecutionH andle parameter.
22.9 Tables used with SQL/MED
1. Rationale: Remove a row that had been forgotten to be removed when a new data retrieval architecture was
introduced.
Delete the following row from Table 33 — Codes used for foreign-data wrapper handle types
Handle type Code
© ISO/IEC 2003 – All rights reserved 9
---------------------- Page: 9 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
DataH andle 5
23.2 invocation
1. Rationale: Add missing text for Success with Information condition.
Insert the following General Rule:
4) a) ii) 1.1) If a comple tion condition is raised: warning, then RC is set to indicate Success with
information.
2. Rationale: Add missing text for Success with Information condition.
Insert the following General Rule:
4) b) iii.1) If RN is a foreign-data wrapper interface wrapper routine, then the actions of the invoking
SQL-server in respo nse to the failed execution of RN are implem entation-de penden t.
23.3.1 AllocWrapperEnv
1. Rationale: Make im plemen tation-defined explicit.
Replace General Rule 3) with:
3) If the implementation-defined maximum number of foreign-data wrapper environments that can be
allocated at o ne time has already be en reache d, then an ex ception co ndition is raised : FDW -specific
condition — limit on number of handles exceeded. A skeleton FDW -environm ent is allocated and is
assigned a unique value that is returned in WrapperEnvHandle.
23.3.3 ConnectServer
1. Rationale: Make im plemen tation-defined explicit.
Replace General Rule 13) with:
13) If the implementation-defined maximum number of FS-connections that can be allocated at one time
has already been reached, then FSConnectionHandle is set to zero and an exception condition is raised:
FDWspecific condition — limit on number of handles exceeded.
23.3.18 InitRequest
1. Rationale: Make im plemen tation-defined explicit.
Replace General Rule 7) with:
7) If the implementation-defined maximum number of FDW-replies that can be allocated at one time has
already be en reache d, then Re plyHan dle is set to zero a nd an exc eption con dition is raised: FDW-
specific condition — limit on number of handles exceeded.
10 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
Replace General Rule 10) with:
10) If the implementation-defined maximum number of FDW-executions that can be allocated at one time
has already been reached, then ExecutionHandle is set to zero and an exception condition is raised:
FDW-specific condition — limit on number of handles exceeded.
2. Rationale: Clarify wh en a desc riptor hand le is used instea d of the desc riptor itself.
Replace General Rule 14) with:
14) Let NIDA be the number of item descriptor areas that must be set up for the server row descriptor. Let
SRDH andle be the DescriptorHandle that is returned by an invocation of the AllocDescriptor()
routine with NIDA as the M axDetailA reas param eter. Let SRD be the server row descriptor identified
by SRDH andle . SRD is associated with the allocated FDW-execution. For this descriptor area, fields
with non -blank entrie s in Table 3 6, “Foreign -data wrap per descrip tor field default v alues”, are se t to
the specified default values by the invocation of the SetDescriptor() routine with SRDH andle as
the DescriptorHandle parameter and r as the Record-N umber parame ter, 1 (one) £ r £ NIDA, and the
code for the fields with no n-blank en tries in Table 3 6, “Foreign -data wrap per descrip tor field default
values”, from Table 32, “Codes used for foreign-data wrapper descriptor fields”, as the FieldIdentifier
parameter. All other fields in the item desc riptor areas of SRD are initially undefined.
23.3.20 Open
1. Rationale: Define previously undefined symbols.
Insert the following General Rule:
5) a.0) Let SRD be the SRDHandle that would be returned by an invocation of the
GetSRDHandle() routine with EH as the Exe cutionH andle para meter. Let SPD be the
SPDHandle that would be returned by an invocation of the GetSPDHandle() routine with
EH as the Exe cutionH andle para meter. Let WRD be the WRDHandle that would be returned
by an invocation of the GetWRDHandle() routine with EH as the Exe cutionH andle
paramete r. Let WPD be the WPDHandle that would be returned by an invocation of the
GetWPDHandle() routine with EH as the ExecutionH andle parameter.
2. Rationale: Define previously undefined symbols.
Replace General Rule 5) with:
5) c) Let TDT be the effective data type of the j-th , for 1 (one) £ £ NCR, as
j j
represented by the values of the TYPE, LENGTH, OCTET_LENGTH, PRECISION, SCALE,
DATETIME_INTERVAL_CODE, DATETIME_INTERVAL_PRECISON,
CHARACTER_SET_CATALOG, CHARACTER_SET_SCHEMA, CHARACTER_SET_NAME,
USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
USER_DEFINED_TYPE_NAME, SCOPE_CATALOG, SCOPE_SCHEMA, and SCOPE_NAME
fields that would be set by separate invocations of the GetDescriptor( ) routine with SRD as
the Desc riptorHan dle param eter, as the RecordNumber parameter, and the code for the fields
j
TYPE, LENGTH, OCTET_LENGTH, PRECISION, SCALE, DATETIME_INTERVAL_CODE,
DATETIME_INTERVAL_PRECISON, CHARACTER_SET_CATALOG,
CHARACTER_SET_SCHEMA, CHARACTER_SET_NAME,
USER_DEFINED_TYPE_CATALOG, USER_DEFINED_TYPE_SCHEMA,
© ISO/IEC 2003 – All rights reserved 11
---------------------- Page: 11 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
USER_DEFINED_TYPE_NAME, SCOPE_CATALOG, SCOPE_SCHEMA, and SCOPE_NAME
from Table 32, ‘‘Codes used for foreign-data wrapper descriptor fields’’, as the FieldIdentifier
parameter. TYPE either indicates ROW or is one of the code values in Table 17, ‘‘Codes used for
application data types in SQ L/CLI’’.
23.3.22 TransmitRequest
1. Rationale: Make im plemen tation-defined explicit.
Replace General Rule 6) with:
6) If the implementation-defined maximum number of FDW-executions that can be allocated at one time
has already been reached, then ExecutionHandle is set to zero and an exception condition is raised:
FDW-specific condition — limit on number of handles exceeded.
2. Rationale: Clarify wh en a desc riptor hand le is used instea d of the desc riptor itself.
Replace General Rules 10), 11), 12), and 13) with:
10) Let SRDItemDescriptorAreas be the number of item descriptor areas that need to be set up for the
server row descriptor. L et SRDH andle be the DescriptorHandle that is returned by an invocation of the
AllocDescriptor() routine with SRDItemDescriptorAreas as the MaxDetailAreas parameter. Let
SRD be the server row descriptor identified by SRDH andle. SRD is associated with the allocated FDW-
execution.
For this desc riptor, fields with non-blank entries in Tab le 36, “Foreig n-data wra pper desc riptor field
default values”, are set to the specified default values by the invocation of the SetDescriptor()
routine with SRDH andle as the DescriptorHandle parameter and r as the Rec ord-Num ber param eter, 1
(one) £ r £ SRDItemDescriptorAreas, and the code for the fields with non-blank entries in Table 36,
“Foreign-d ata wrapp er descriptor fie ld default valu es”, from T able 32, “C odes used for foreign-da ta
wrapper descriptor fields”, as the FieldIdentifier parameter. All other fields in the item descriptor areas
of SRD are initially undefined.
11) Let SPDItemDescriptorAreas be the number of item descriptor areas that need to be set up for the
server para meter desc riptor. Let SPDH andle be the DescriptorHandle that is returned by an invocation
of the AllocDescriptor() routine with SPDItemDescriptorAreas as the MaxDetailAreas
paramete r. Let SPD be the server parameter descriptor identified by SPDH andle. SPD is associated
with the allocated FDW-execution.
For this desc riptor, fields with non-blank entries in Tab le 36, “Foreig n-data wra pper desc riptor field
default values”, are set to the specified default values by the invocation of the SetDescriptor()
routine with SPDH andle as the DescriptorHandle parameter and r as the Rec ord-Num ber param eter, 1
(one) £ r £ SPDItemDescriptorAreas, and the code for the fields with non-blank entries in Table 36,
“Foreign-d ata wrapp er descriptor fie ld default valu es”, from T able 32, “C odes used for foreign-da ta
wrapper descriptor fields”, as the FieldIdentifier parameter. All other fields in the item descriptor areas
of SPD are initially undefined.
12) Let WRDItemDescriptorAreas be the number of item descriptor areas that need to be set up for the
wrappe r row desc riptor. Let WRD Handle be the DescriptorHandle that is returned by an invocation of
the AllocDescriptor() routine with WRDItemDescriptorAreas as the MaxDetailAreas
paramete r. Let WRD be the wrapper row descriptor identified by WRD Handle . WRD is associated with
12 © ISO/IEC 2003 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/IEC 9075-9:2001/Cor.1:2003(E)
the allocated FDW-execution.
For this desc riptor, fields with non-blank entries in Tab le 36, “Foreig n-data wra pper desc riptor field
default values”, are set to the specified default values by the invocation of the SetDescriptor()
routine with WRD Handle as the DescriptorHandle parameter and r as the Rec ord-Num ber param eter, 1
(one) £ r £ WRDItemDescriptorAreas, and the code for the fields with non-blank entries in Table 36,
“Foreign-d ata wrapp er descriptor fie ld default valu es”, from T able 32, “C odes used for foreign-da ta
wrapper descriptor fields”, as the FieldIdentifier parameter. All other fields in the item descriptor areas
of WRD are initially undefined.
13) Let WPDItemDescriptorAreas be the number of item descriptor areas that need to be set
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.