[0.1] the database_transaction_isolation_and_concurrency_c subdomain of database transaction isolation and concurrency control (164 concepts)
Skills in this repository
sancovp/dark-factory-live - Page 17
SkillsMP has collected 831 skills from sancovp/dark-factory-live. Open a skill to review its source and details.
sancovp/dark-factory-liveShowing 40 of 831 collected skills.
[0.1.1] The all-or-nothing property: a transaction's effects are either fully applied or fully absent; implemented via
[0.1.2] A configurable parameter defining the degree to which concurrent transactions are isolated from each other's u
[0.1.4] An isolation_level where each statement sees only data committed before that statement begins; prevents dirty_
[0.1.3] The act of undoing a transaction's effects using undo_log entries, returning the database to its pre-transacti
[0.1.6] Lock management at the individual row granularity via row_lock entries in lock_manager's lock table; enables h
[0.1.5] The current phase of a transaction lifecycle: active, partially_committed, committed, aborted; drives lock rel
[0.2] the deep_database_transaction subdomain of database transaction isolation and concurrency control (24 concepts)
[0.2.5] A special log_record written periodically by a checkpoint_writer; records the volatile database state at a con
[0.2.6] The act of transferring the contents of tl_log_buffer to durable storage; triggered by transaction commit, tl_
[0.2.1] The fundamental unit of a transaction_log: a single append-only entry recording one atomic change or lifecycle
[0.2.2] The subsystem that, on system restart, reads the transaction_log from the last tl_checkpoint_record forward; r
[0.2.4] A structured collection of tl_update_record entries chained by a transaction; traversed in reverse order durin
[0.2.3] A log_record capturing a before_image and after_image of a modified data page or row; used by both redo_recove
[0.3] the deep_isolation_level subdomain of database transaction isolation and concurrency control (29 concepts)
[0.3.1] temporal threshold in read_committed: a datum is visible iff its committing_transaction committed before the r
[0.3.3] database state resulting from successfully completed transactions; constitutes the visible universe for read_c
[0.3.6] lock management characteristic in read_committed where shared read locks are typically released immediately af
[0.3.4] guarantee within read_committed that each SQL statement sees all changes committed at the moment that statemen
[0.3.5] A modification to database state made by a transaction that has not yet committed; visible to other transactio
[0.3.2] exclusive lock discipline in read_committed requiring a transaction to hold write locks on modified rows until
[0.1.1] The all-or-nothing property: a transaction's effects are either fully applied or fully absent; implemented via
[0.1.2] A configurable parameter defining the degree to which concurrent transactions are isolated from each other's u
[0.1.3] The act of undoing a transaction's effects using undo_log entries, returning the database to its pre-transacti
[0.1.4] An isolation_level where each statement sees only data committed before that statement begins; prevents dirty_
[0.1.5] The current phase of a transaction lifecycle: active, partially_committed, committed, aborted; drives lock rel
[0.1.6] Lock management at the individual row granularity via row_lock entries in lock_manager's lock table; enables h
[0.1] the database_transaction_isolation_and_concurrency_c subdomain of database transaction isolation and concurrency control (164 concepts)
[0.2.1] The fundamental unit of a transaction_log: a single append-only entry recording one atomic change or lifecycle
[0.2.2] The subsystem that, on system restart, reads the transaction_log from the last tl_checkpoint_record forward; r
[0.2.3] A log_record capturing a before_image and after_image of a modified data page or row; used by both redo_recove
[0.2.4] A structured collection of tl_update_record entries chained by a transaction; traversed in reverse order durin
[0.2.5] A special log_record written periodically by a checkpoint_writer; records the volatile database state at a con
[0.2.6] The act of transferring the contents of tl_log_buffer to durable storage; triggered by transaction commit, tl_
[0.2] the deep_database_transaction subdomain of database transaction isolation and concurrency control (24 concepts)
[0.3.1] temporal threshold in read_committed: a datum is visible iff its committing_transaction committed before the r
[0.3.2] exclusive lock discipline in read_committed requiring a transaction to hold write locks on modified rows until
[0.3.3] database state resulting from successfully completed transactions; constitutes the visible universe for read_c
[0.3.4] guarantee within read_committed that each SQL statement sees all changes committed at the moment that statemen
[0.3.5] A modification to database state made by a transaction that has not yet committed; visible to other transactio