sancovp/database-transaction-isolation-and-concu-module

0-1-1-understand-abort-reason

[0.1.1] The specific cause that precipitated a transaction's transition to the aborted_state, such as a constraint vio

0-1-2-understand-aborted-data

[0.1.2] The intermediate state of rows modified by a transaction that later aborted; the partial_effects_undone that e

0-1-3-understand-recovery-log-entry

[0.1.3] A durable record written to the transaction log capturing a single row modification, containing the transactio

0-1-4-understand-automatic-restart-forbidden

[0.1.4] A protocol constraint requiring that a transaction in the aborted_state cannot be re-executed automatically by

0-1-5-understand-lock-release

[0.1.5] The deterministic act of relinquishing every lock held by a transaction upon reaching its transaction_boundary

0-1-6-understand-partial-effects-undone

[0.1.6] The invariant that upon rollback all modifications performed by the transaction are reversed to match the befo

0-1-understand-core

[0.1] the core subdomain of database transaction isolation and concurrency control (17 concepts)

0-2-1-understand-atomicity

[0.2.1] The all-or-nothing property: a transaction's effects are either fully applied or fully absent; implemented via

0-2-2-understand-isolation-level

[0.2.2] A configurable parameter defining the degree to which concurrent transactions are isolated from each other's u

0-2-3-understand-aborted-state

[0.2.3] The terminal transaction_state after rollback completes; all acquired locks are released and the transaction c

0-2-4-understand-rollback

[0.2.4] The act of undoing a transaction's effects using undo_log entries, returning the database to its pre-transacti

0-2-5-understand-transaction-state

[0.2.5] The current phase of a transaction lifecycle: active, partially_committed, committed, aborted; drives lock rel

0-2-6-understand-read-committed

[0.2.6] An isolation_level where each statement sees only data committed before that statement begins; prevents dirty_

0-2-understand-database-transaction-isolation-and-concurrency-c

[0.2] the database_transaction_isolation_and_concurrency_c subdomain of database transaction isolation and concurrency control (164 concepts)

0-3-1-understand-tl-log-record

[0.3.1] The fundamental unit of a transaction_log: a single append-only entry recording one atomic change or lifecycle

0-3-2-understand-rr-definition

[0.3.2] An isolation_level ensuring that all reads within a transaction see a consistent snapshot of the database as o

0-3-3-understand-tl-recovery-manager

[0.3.3] The subsystem that, on system restart, reads the transaction_log from the last tl_checkpoint_record forward; r

0-3-4-understand-dur-write-ahead-logging

[0.3.4] A protocol mandating that log records describing modifications be flushed to durable_storage before the corres

0-3-5-understand-dur-recovery-manager

[0.3.5] The subsystem that enforces durability by reconstructing the committed database state from transaction_log aft

0-3-6-understand-rr-read-lock

[0.3.6] A shared_lock acquired when a row is read under repeatable_read; held until transaction commits or rolls back,

0-3-understand-deep-database-transaction

[0.3] the deep_database_transaction subdomain of database transaction isolation and concurrency control (47 concepts)

Source text: Undetermined

0-4-1-understand-committed-data

[0.4.1] database state resulting from successfully completed transactions; constitutes the visible universe for read_c

0-4-2-understand-commit-visibility-boundary

[0.4.2] temporal threshold in read_committed: a datum is visible iff its committing_transaction committed before the r

0-4-3-understand-write-lock-held-until-commit

[0.4.3] exclusive lock discipline in read_committed requiring a transaction to hold write locks on modified rows until

0-4-4-understand-statement-level-read-consistency

[0.4.4] guarantee within read_committed that each SQL statement sees all changes committed at the moment that statemen

0-4-5-understand-uncommitted-change

[0.4.5] A modification to database state made by a transaction that has not yet committed; visible to other transactio

0-4-6-understand-lock-timeout-handling

[0.4.6] timeout mechanism in read_committed for transactions blocked waiting to acquire conflicting locks on rows

0-4-understand-deep-isolation-level

[0.4] the deep_isolation_level subdomain of database transaction isolation and concurrency control (29 concepts)

0-5-1-understand-c009

[0.5.1] commit completion: the terminal state transition from active to committed; releases all locks held exclusively

0-5-2-understand-c001

[0.5.2] commit point: the precise instant when a transaction transitions from active to committed; the log sequence nu

0-5-3-understand-c002

[0.5.3] commit log record: the write-ahead log entry that atomically records the commit point; contains transaction id

0-5-4-understand-c003

[0.5.4] commit sequence number (CSN): a monotonically incrementing identifier assigned to each committed transaction;

0-5-5-understand-c004

[0.5.5] commit durability: the guaranteed persistence property that all writes of a committed transaction survive syst

0-5-6-understand-c005

[0.5.6] commit visibility: the isolation property that all writes of a committed transaction become visible to subsequ

0-5-understand-deep-rollback

[0.5] the deep_rollback subdomain of database transaction isolation and concurrency control (23 concepts)

using-database-transaction-isolation-and-concu

Use the database transaction isolation and concurrency control neurosymbolic module: RAG library, agent brain, growable KB — proof-checked