204 RDBLOCK= Data Set Option Chapter 10
All of the rows that are part of the current commit batch are rejected, and you must
re-enter or modify all the rows of data that you have entered since the previous
commit. This causes the constraint evaluation to be deferred until commit time, as in
Release 6.12 of the SAS/ACCESS Interface to Oracle Rdb.
ON
causes all of the affected constraints to be evaluated after each row (or observation)
is entered or updated. If your data violates a NULL constraint, then you are
informed immediately, and only the current record is rejected. When
RDBCONST=ON is speciļ¬ed, the SET DEFAULT CONSTRAINTS ON statement is
executed immediately after you are connected to the database. It is re-executed after
each commit because the statement remains in effect for only one transaction.
Details
The RDBCONST= option corresponds to the execution of the following Oracle Rdb SQL
statements:
SAS Option Value Oracle Rdb SQL Statement
RDBCONST=ON SET DEFAULT CONSTRAINTS ON
RDBCONST=OFF SET DEFAULT CONSTRAINTS OFF
Example
The following example shows how to specify the RDBCONST= option in a view
descriptor that is based on Oracle Rdb data. This example references a previously
created view descriptor named VLIB.INVOICE.
proc fsedit data=adlib.allinv(rdbconst=on);
run;
RDBLOCK= Data Set Option
Enables multiple users to update data in a table concurrently
Valid in: DATA and PROC steps (when accessing DBMS data using PROC ACCESS,
PROC DBLOAD, or the Pass-Through Facility)
DBMS support: Oracle Rdb
Default value:
NOCONCUR
Syntax
RDBLOCK= CONCUR | NOCONCUR
Syntax Description
