Table of Contents
Advertisement
Isolation levels
GRANT, REVOKE,
and SET OPTION are
not restricted
Primary keys and locking
Isolation levels
302
While the commands
GRANT
DDL operations, they cause no concurrency conflicts, and so are not restricted.
and
always cause an automatic commit;
GRANT
REVOKE
an automatic commit except when it is specified as
are not allowed for any user currently connected to the database.
REVOKE
affects all subsequent SQL statements sent to the database server,
OPTION
except for certain options that do not take effect until after you restart the
database server. See the Adaptive Server IQ Reference Manual for details of
setting options.
Because only one user can update a table, primary key generation does not
cause concurrency conflicts.
An important aspect of transaction processing is the database server's ability to
isolate an operation. ANSI standards define four levels of isolation. Each
higher level provides transactions a greater degree of isolation from other
transactions, and thus a greater assurance that the database remains internally
consistent.
The isolation level controls the degree to which operations and data in one
transaction are visible to operations in other, concurrent transactions. IQ
snapshot versioning supports the highest level of isolation. At this level, all
schedules may be serialized.
Snapshot versioning maintains this high level of isolation between concurrent
transactions by following these rules:
•
Transaction management maintains a snapshot of committed data at the
time each transaction begins.
•
A transaction can always read, as long as the snapshot version it uses is
maintained.
•
A transaction's writes are reflected in the snapshot it sees.
•
Once a transaction begins, updates made by other transactions are
invisible to it.
,
, and
REVOKE
SET OPTION
TEMPORARY
are also considered
causes
SET OPTION
.
and
GRANT
SET
Advertisement
Table of Contents
