(B)0[m[4mSTORE[m qqwqqqqqqqqqqq>qqqqqqqqqqqqwqqqqqqk
mqqqq> handle-options qqqj x
lqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqj
mq> context-var qq> [4mIN[m qwqqqqqqqqq>qqqqqqqqqqwqq> relation-name qqk
mq> db-handle qq> . qj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mq> [4mUSING[m qwqqqqqqq>qqqqqqwq> store-items qqq> [4mEND_STORE[m qq>
mqq> on-error qj
(The optional GET...RDB$DB_KEY is available only in programs
preprocessed by the RDBPRE preprocessor. The optional
PRINT...RDB$DB_KEY can be used in RDO only.)
1 – handle-options
(B)0[mhandle-options =
qq> ( qwq> [4mREQUEST_HANDLE[m qqq> var qqqqqqqqqqqqqqqqqqqqqqqqqqqwq> ) qq>
tq> [4mTRANSACTION_HANDLE[m qqq> var qqqqqqqqqqqqqqqqqqqqqqqu
mq> [4mREQUEST_HANDLE[m q> var , [4mTRANSACTION_HANDLE[m q> var qj
1.1 – REQUEST_HANDLE
A keyword followed by a host language variable. A request handle
points to the location of a compiled Oracle Rdb request. If you
do not supply a request handle explicitly, Oracle Rdb associates a
default request handle with the compiled request. You must use
a request handle to make an identical query to two different
databases.
In Callable RDO, use !VAL as a marker for host language
variables.
You can put parentheses around the host language variable name.
1.2 – TRANSACTION_HANDLE
A keyword followed by a host language variable. A transaction
handle identifies each instance of a transaction. If you do not
declare the transaction handle explicitly, Oracle Rdb attaches an
internal identifier to the transaction.
In Callable RDO, use !VAL as a marker for host language
variables.
You can put parentheses around the host language variable name.
Normally, you do not need to use this argument. The ability to
declare a transaction handle is provided for compatibility with
other database products and future releases of Oracle Rdb.
2 – context-var
A valid context variable.
3 – db-handle
A host language variable used to refer to the database.
4 – relation-name
The name of the relation into which the value is stored.
5 – store-items
(B)0[mstore-items = qwqwq> context-var . field-name qqq> = qqq> value-expr qqwqqqwqqqk x mqqqqqqqqqqqqqqqqqqqqqqqq ; <qqqqqqqqqqqqqqqqqqqqqqqqqj x x mqqq> context-var . * qqqqqqqqqq> = qq> record-descr qqqqqqqj x lqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqj mwqqqqqqqqqqqqqqqqqqqqqqqqqqqq>qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqwq> tq> [4mGET[m qq> host-var q> = qq> context-var qq> . qq> [4mRDB$DB_KEY[m qu mq> [4mPRINT[m qqqqqqqqqqqqqqqqqqq> context-var qq> . qq> [4mRDB$DB_KEY[m qj
5.1 – field-name
The name of the field in the relation where the value is stored.
5.2 – value-expr
A valid Oracle Rdb value expression that specifies the value to be
stored. For more information, request HELP on Value_expr.
5.3 – record-descr
A valid data dictionary record descriptor matching all the fields
of the relation.
5.4 – GET...RDB$DB_KEY
In an RDBPRE program (BASIC, COBOL, FORTRAN), you can use
GET...RDB$DB_KEY to retrieve the database key of the record
about to be stored by the STORE statement into a host language
variable. Example:
&RDB& STORE E IN EMPLOYEES USING E.EMPLOYEE_ID = 15231;
&RDB& E.LAST_NAME = "Smith";
&RDB& GET MY_DB_KEY = E.RDB$DB_KEY;
&RDB& END_GET
&RDB& END_STORE
(MY_DB_KEY is a user-defined host language variable.)
(The optional GET...RDB$DB_KEY is available only in programs
preprocessed by the RDBPRE preprocessor. The optional
PRINT...RDB$DB_KEY can be used in RDO only.)
5.5 – PRINT...RDB$DB_KEY
In RDO only, you can use PRINT...RDB$DB_KEY to display the
database key of the record about to be stored by the STORE
statement. Example:
RDO> STORE E IN EMPLOYEES USING
cont> E.EMPLOYEE_ID = "15231";
cont> E.LAST_NAME = "Smith";
cont> PRINT E.RDB$DB_KEY
cont> END_STORE
RDB$DB_KEY
21:339:0
6 – on-error
The ON ERROR clause, which specifies a host language statement or
Oracle Rdb data manipulation statement to be performed if an Oracle Rdb
error occurs. For more information, request HELP on ON_ERROR.