(B)0[mreserving-clause =
qqwqwqqqqqqqq>qqqqqqqqqqqqwqwq> relation-name qqwqwqqqk
x mq> db-handle qq> . qqj mq> view-name qqqqqqj x x
mqqqqqqqqqqqqqqqqqq , <qqqqqqqqqqqqqqqqqqqqqqqqqj x
x
lqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mq> [4mFOR[m qqqwqqqqqqqq>qqqqqqqqqwqqqqwqq> [4mREAD[m qqqwqqq>
tqq> [4mEXCLUSIVE[m qqqqu mqq> [4mWRITE[m qqj
tqq> [4mPROTECTED[m qqqqu
mqq> [4mSHARED[m qqqqqqqj
1 – More
The list of relations to be locked during the transaction.
In general, include all the relations your transaction will
access. If you specify the AUTO LOCKING clause, constraints and
triggers defined on the reserved relations will be able to access
additional relations that do not appear in the list of reserved
relations.
Note that if you use the RESERVING clause without the AUTO
LOCKING clause, you can access only those relations that you
have explicitly reserved.
2 – Options
Option Access Constraints
SHARED Other users can work with the same relations
as you. Depending on the option they choose,
they can have read-only or read and write
access to the relations.
PROTECTED Other users can read the relations you are
using. They cannot have WRITE access.
EXCLUSIVE Other users cannot read records from the
relations included in your transaction. If
another user refers to the same relation in
a START_TRANSACTION statement, Oracle Rdb denies
access to that user.
READ You will only read data from the relations.
WRITE You will store, modify, or erase data in
the relations.