Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Transaction - a sequence of atomic (either all occurs, or nothing occurs) logically related action(s) actions over the database , which moves it objects.

Atomicity - a transaction property which declares: either all actions are carried out or none are.

Consistency - a transaction property which moves a database from one consistent state to another. A meaning of the consistent state is defined by a user.

Isolation - a measure of mutual influence between concurrent interleaved transactions.

Durability - a property which guarantees that database state remains unchanged after a transaction is committed, despite any failures.

Transaction executionSchedule - a sequence of reads and writes belonging to a single transactionway of executing interleaved transactions.

Serializable schedule - a schedule where all transactions are executed sequentially.

Concurrency control (CC) - a technique to preserve database consistency in case of interleaved executions.Serializable execution - a transaction execution, equivalent to some serial execution of interleaved transactionsnon-serializable schedules.

Multi-version concurrency control (MVCC) - a family of concurrency control techniques based on writing multiple record versions (copy-on-write). Reduces a Eliminates blocking between reads and writes.

Recoverable executionschedule - a transaction execution which is not affected by aborting of some other transaction. A transaction reads only committed values to achieve this.

Transactions history - a set of concurrent transaction executions.

Serializable history - a history representing serializable execution.

Interactive transaction - a transaction whose operation set is not known in advanceapriory. Can be aborted at any time before commit, if not committed yet.

Design Goals

Description

// Provide the design of the solution.

...