|
Transactions allow a number of updates to be executed as a
single atomic operation. An atomic operation ensures that
if any of the updates fail the transaction is terminated
and the preceding updates are rolled back to leave the
affected data in the same state as previously existed.
CodeMatrix transactions support all update operations,
including those that affect the client computer such as
mount and checkout. Two phase commit techniques ensure
that the client and server computers are consistent even
after critical errors.
Care should be taken when using transactions, as any
database locks taken remain active until the transaction
completes, therefore any transaction should be kept as
short as possible to avoid locking out other users.
The CodeMatrix application uses transactions
by default when performing any multiple update.
If using the command line client the begin,
end and rollback commands are used as in the following
example
| |
begin
add c:\my documents\projectspec.doc //documents/projectspec.doc
add c:\my documents\projectspec2.doc
//documents/projectspec2.doc
end
|
See also:
The command line
begin command
The command line
end command
The command line
rollback command
Using
transactions
Administering
transactions
|
