Mapping members of MapVar1
variable with columns of Table1
of Connection1 is cleared.
Members of MapVar1 variable
are mapped with columns of
Table2 of Connection2.
ï‚– Restrictions on Mapping to Multiple SQL Types
You cannot map a DB Map Variable for two or more SQL types.
If you execute multiple DB_CreateMapping (Create DB Map) instructions so as to map a single
DB Map Variable for two or more SQL types, the mapping made by the last DB_CreateMapping
(Create DB Map) instruction takes effect.
Example:
Members of MapVar1 variable
are mapped with columns of
Table1.
Mapping members of MapVar1
variable with columns of Table1
for INSERT is cleared.
Members of MapVar1 variable
are mapped with columns of
Table1 for UPDATE.
ï‚– Number of DB Map Variables for which Mapping can be Created
The total number of DB Map Variables for which you can create a mapping in all connections
depends on the database type to connect. Refer to 1-2-1 DB Connection Service Specifications
for the number of DB Map Variables supported for each DB. When the upper limit is exceeded,
an instruction error (Data Capacity Exceeded) will occur when a DB_CreateMapping (Create DB
Map) instruction is executed.
However, even if the number of DB Map Variables has not reached the upper limit, an instruction
error (Data Capacity Exceeded) will occur when the total number of members of structures used
as data type of DB Map Variables in all DB Connections exceeds 10,000 members.
Connection1
‘Table1’
MapVar1
_DB_SQLTYPE_UPDATE