최근 바뀜
IT 위키
이 페이지에서 위키의 최근 바뀜을 추적합니다.
약어 목록:
- 새글
- 새 문서 (새 문서 목록도 보세요)
- 잔글
- 사소한 편집
- 봇
- 봇이 수행한 편집
- (±123)
- 바이트 수로 표현한 문서 크기의 차이
2024년 12월 24일 (화)
| 07:50 | 사용자 만들기 기록 Bekil kupil *982 cswiki.net 3J 토론 기여 계정이 생성되었습니다 | ||||
2024년 12월 21일 (토)
| 06:22 | 사용자 만들기 기록 Bekil kupil *982 cswiki.net Cq 토론 기여 계정이 생성되었습니다 | ||||
2024년 12월 18일 (수)
|
|
22:56 | (사용자 만들기 기록) [Phiker mik *547 cswiki.net S7; Bula dinor 000x cswiki.net cs; Bekil kupil *982 cswiki.net ly] | |||
|
|
22:56 Phiker mik *547 cswiki.net S7 토론 기여 계정이 생성되었습니다 | ||||
|
|
18:23 Bekil kupil *982 cswiki.net ly 토론 기여 계정이 생성되었습니다 | ||||
|
|
14:34 Bula dinor 000x cswiki.net cs 토론 기여 계정이 생성되었습니다 | ||||
| 새글 07:21 | 분류:Information Science 차이역사 +523 141.101.98.238 토론 (Created page with "Hi there, We run a YouTube growth service, which increases your number of subscribers both safely and practically. - We guarantee to gain you 700-1500+ subscribers per month. - People subscribe because they are interested in your channel/videos, increasing likes, comments and interaction. - All actions are made manually by our team. We do not use any 'bots'. The price is just $60 (USD) per month, and we can start immediately. If you have any questions, let me know, a...") | ||||
2024년 12월 17일 (화)
| 12:10 | 사용자 만들기 기록 JamesWerly 토론 기여 계정이 생성되었습니다 | ||||
2024년 12월 16일 (월)
| 새글 03:03 | Distributed Two-Phase Locking 차이역사 +4,665 Betripping 토론 기여 (Created page with "'''Distributed Two-Phase Locking (Distributed 2PL)''' is a concurrency control protocol used in distributed database systems to ensure global serializability. In this protocol, each site manages locks independently while coordinating with other sites to maintain consistency across the distributed system. ==Key Concepts== *'''Global Serializability:''' Ensures that the execution of distributed transactions is equivalent to a serial execution. *'''Distributed Lock Manageme...") | ||||
| 새글 02:48 | Primary Copy Two-Phase Locking 차이역사 +4,224 Betripping 토론 기여 (Created page with "'''Primary Copy Two-Phase Locking (2PL)''' is a concurrency control protocol used in distributed database systems where a primary copy of each data item is designated for lock management. Transactions must obtain locks from the primary copy of the data item to ensure consistency and serializability across the system. ==Key Concepts== *'''Primary Copy:''' A specific node in the distributed system is designated as the authoritative source for managing locks for a particula...") | ||||
| 새글 02:36 | Primary Site Two-Phase Locking 차이역사 +3,711 Betripping 토론 기여 (Created page with "'''Primary Site Two-Phase Locking (2PL)''' is a variant of the Two-Phase Locking protocol used in distributed databases. In this approach, one node is designated as the primary site for each data item, and it coordinates the locking and transaction processing to ensure serializability across the system. ==Key Concepts== *'''Primary Site:''' A designated node that manages all lock requests for a specific data item. *'''Global Serializability:''' Ensures that all transacti...") | ||||
| 새글 02:35 | Distributed Database 차이역사 +5,341 Betripping 토론 기여 (Created page with "'''Distributed Database''' is a collection of databases distributed across multiple physical locations that function as a single logical database. Each site can operate independently while participating in a unified database system through communication over a network. ==Key Concepts== *'''Data Distribution:''' Data is distributed across multiple sites based on factors like performance, reliability, and locality. *'''Transparency:''' Users interact with the distributed d...") | ||||
| 새글 02:29 | Distributed Computing 차이역사 +4,523 Betripping 토론 기여 (Created page with "'''Distributed Computing''' is a field of computer science that involves a collection of independent computers working together as a single cohesive system. These computers, or nodes, communicate over a network to achieve a common goal, such as solving complex problems, processing large datasets, or enabling fault-tolerant services. ==Key Concepts== *'''Distributed System:''' A collection of independent computers that appear to the user as a single system. *'''Concurrenc...") | ||||
| 새글 02:27 | Distributed Query Processing 차이역사 +4,991 Betripping 토론 기여 (Created page with "'''Distributed Query Processing''' is the process of executing database queries across multiple interconnected nodes in a distributed database system. It involves decomposing a high-level query into sub-queries that are executed on different nodes, combining the results, and presenting a unified output to the user. ==Key Concepts== *'''Distributed Database:''' A collection of interconnected databases located on different physical sites. *'''Query Decomposition:''' Breaki...") | ||||
2024년 12월 14일 (토)
| 04:26 | 사용자 만들기 기록 Bekil kupil *982 cswiki.net n9 토론 기여 계정이 생성되었습니다 | ||||
2024년 12월 13일 (금)
| 새글 01:40 | Multiversion Concurrency Control 차이역사 +3,490 Scapegoat 토론 기여 (Created page with "'''Multiversion Concurrency Control (MVCC)''' is a concurrency control method used in database systems that allows multiple versions of a data item to exist simultaneously. It ensures consistent reads without locking and provides high concurrency by maintaining transaction isolation. ==Key Concepts== *'''Data Versioning:''' MVCC creates a new version of a data item for every write operation, enabling transactions to access consistent snapshots. *'''Timestamps:''' Each tr...") | ||||
| 새글 01:39 | Timestamp-Based Protocol 차이역사 +3,700 Scapegoat 토론 기여 (Created page with "'''Timestamp-Based Protocol''' is a concurrency control mechanism in database systems that uses timestamps to order transactions, ensuring serializability. Each transaction is assigned a unique timestamp when it begins, and the protocol uses these timestamps to determine the execution order of conflicting operations. ==Key Concepts== *'''Timestamp:''' A unique identifier (usually based on the system clock or a counter) assigned to each transaction when it starts. *'''Rea...") | ||||
| 새글 01:35 | Lock-Based Protocol 차이역사 +3,804 Scapegoat 토론 기여 (Created page with "'''Lock-Based Protocol''' is a concurrency control mechanism in database systems that ensures transaction isolation by managing access to data items through locks. Locks prevent simultaneous transactions from interfering with each other, ensuring data consistency and serializability. ==Key Concepts== *'''Lock:''' A mechanism that restricts access to a data item for concurrent transactions. *'''Lock Modes:''' **'''Shared Lock (S):''' Allows multiple transactions to read a...") | ||||
| 새글 01:33 | Two-Phase Locking 차이역사 +3,740 Scapegoat 토론 기여 (Created page with "'''Two-Phase Locking (2PL)''' is a concurrency control protocol used in database systems to ensure serializability of transactions. It operates in two distinct phases where locks are acquired and released in a specific order, preventing conflicts between concurrent transactions. ==Key Concepts== *'''Locking Protocol:''' Transactions acquire locks on data items before accessing them and release locks when no longer needed. *'''Serializability:''' 2PL guarantees that the r...") | ||||
| 새글 01:31 | Concurrency Control 차이역사 +3,880 Scapegoat 토론 기여 (Created page with "'''Concurrency Control''' is a mechanism in database management systems (DBMS) that ensures correct and consistent transaction execution in a multi-user environment. It prevents issues such as data inconsistencies and anomalies by managing simultaneous access to the database. ==Key Concepts== *'''Transaction:''' A sequence of database operations that are executed as a single logical unit of work. *'''Isolation:''' Ensures that each transaction is executed independently w...") | ||||
|
|
새글 01:28 | Isolation Level (Database) 2개 바뀜 역사 +4,095 [Scapegoat (2×)] | |||
|
|
01:28 (최신 | 이전) +472 Scapegoat 토론 기여 | ||||
| 새글 |
|
01:28 (최신 | 이전) +3,623 Scapegoat 토론 기여 (Created page with "'''Isolation Level''' is a property in database transaction management that defines the extent to which transactions are isolated from each other. It determines how and when changes made by one transaction are visible to other concurrent transactions, affecting the trade-off between consistency and concurrency. ==Key Concepts== *'''Transaction Isolation:''' Ensures that concurrent transactions do not interfere with each other inappropriately. *'''Anomalies:''' Lower isol...") 태그: 시각 편집 | |||
|
|
새글 01:26 | Non-Repeatable Read 2개 바뀜 역사 +3,785 [Scapegoat (2×)] | |||
|
|
01:26 (최신 | 이전) +22 Scapegoat 토론 기여 태그: 시각 편집 | ||||
| 새글 |
|
01:26 (최신 | 이전) +3,763 Scapegoat 토론 기여 (Created page with "'''Non-Repeatable Read''' is a concurrency problem in database systems that occurs when a transaction reads the same data twice and gets different results due to modifications made by another transaction in the meantime. This inconsistency arises when isolation levels do not guarantee stability for repeated reads of the same data. ==Key Concepts== *'''Unstable Reads:''' The data read by a transaction changes during its execution because another transaction modifies it. *...") 태그: 시각 편집 | |||
| 새글 01:26 | Dirty Read (Database) 차이역사 +3,626 Scapegoat 토론 기여 (Created page with "'''Dirty Read''' is a concurrency problem in database systems that occurs when a transaction reads uncommitted changes made by another transaction. This can lead to inconsistent or incorrect data being used in the reading transaction, especially if the changes are later rolled back. ==Key Concepts== *'''Uncommitted Data:''' Data modified by a transaction that has not yet been committed to the database. *'''Concurrency Issue:''' Dirty reads are a type of Database Anomal...") | ||||
| 새글 01:23 | Precedence Graph 차이역사 +2,874 Scapegoat 토론 기여 (Created page with "'''Precedence Graph''', also known as a '''Serializability Graph''', is a directed graph used in database systems to determine the serializability of a transaction schedule. The graph represents the order of operations across transactions and helps identify potential conflicts that could prevent a schedule from being equivalent to a serial schedule. ==Key Concepts== *'''Nodes:''' Represent individual transactions in the schedule. *'''Edges:''' Indicate a precedence (or d...") | ||||
| 01:20 | 사용자 만들기 기록 Scapegoat 토론 기여 계정이 생성되었습니다 | ||||
2024년 12월 12일 (목)
|
|
16:40 | (사용자 만들기 기록) [Phiker mik *547 cswiki.net fg; By jeong] | |||
|
|
16:40 By jeong 토론 기여 계정이 생성되었습니다 | ||||
|
|
16:20 Phiker mik *547 cswiki.net fg 토론 기여 계정이 생성되었습니다 | ||||
| 새글 07:49 | Serializable (Database) 차이역사 +4,608 Betripping 토론 기여 (Created page with "'''Serializable''' is the highest level of isolation in database transaction management, ensuring that the outcome of concurrent transactions is equivalent to some sequential (serial) execution of those transactions. It prevents issues like dirty reads, non-repeatable reads, and phantom reads, guaranteeing the consistency of the database. ==Key Concepts== *'''Isolation Level:''' Serializable is one of the Isolation Levels defined in the SQL standard, providing the st...") | ||||
2024년 12월 11일 (수)
| 15:29 | 사용자 만들기 기록 오오라블랙 토론 기여 계정이 생성되었습니다 | ||||
|
|
06:41 | Main Page 2개 바뀜 역사 +635 [Betripping (2×)] | |||
|
|
06:41 (최신 | 이전) +40 Betripping 토론 기여 태그: 시각 편집: 전환됨 | ||||
|
|
06:36 (최신 | 이전) +595 Betripping 토론 기여 태그: 시각 편집: 전환됨 | ||||
| 새글 06:33 | ARIES (Database) 차이역사 +19 Betripping 토론 기여 (Redirected page to ARIES) | ||||
|
|
06:29 | ARIES 4개 바뀜 역사 +4,217 [Betripping (4×)] | |||
|
|
06:29 (최신 | 이전) −11 Betripping 토론 기여 태그: 시각 편집 | ||||
|
|
06:26 (최신 | 이전) +711 Betripping 토론 기여 태그: 시각 편집: 전환됨 | ||||
|
|
06:02 (최신 | 이전) +452 Betripping 토론 기여 태그: 시각 편집: 전환됨 | ||||
|
|
06:01 (최신 | 이전) +3,065 Betripping 토론 기여 태그: 시각 편집 | ||||
| 새글 06:23 | Write-Ahead Logging 차이역사 +3,853 Betripping 토론 기여 (Created page with "'''Write-Ahead Logging (WAL)''' is a technique used in database management systems (DBMS) to ensure the '''durability''' and '''atomicity''' of transactions. WAL ensures that all changes to the database are recorded in a log before the changes are written to the database itself. This enables reliable crash recovery and consistency in case of a failure. ==Key Concepts== *'''Sequential Logging:''' All modifications are recorded sequentially i...") | ||||
| 새글 06:19 | Durability (ACID) 차이역사 +2,966 Betripping 토론 기여 (Created page with "'''Durability''' is one of the four key properties in the ACID Properties of database transactions, ensuring that once a transaction has been committed, its changes are permanently saved in the database. This guarantees that data is not lost even in the event of a system crash, power failure, or hardware malfunction. ==Key Concepts== *'''Transaction Commit:''' Durability ensures that when a transaction is committed, its effects are persisted. *'''Non-...") | ||||
| 새글 05:39 | 분류:Database 차이역사 +1,769 Betripping 토론 기여 (Created page with "Database category includes topics related to the design, implementation, and management of databases. It covers various database types, concepts, protocols, and tools that enable efficient storage, retrieval, and manipulation of data. ==Topics in This Category== The following are key areas within the database category: ===Database Concepts=== *Relational Databases *NoSQL Databases *Data Warehousing *Database Normalization *ACID Properties *Database...") | ||||
| 새글 05:38 | Multiple Granularity Locking 차이역사 +4,134 Betripping 토론 기여 (Created page with "'''Multiple Granularity Locking''' is a concurrency control mechanism used in database systems to improve performance and manage locks at various levels of granularity, such as tuples, pages, tables, or the entire database. By allowing transactions to lock data items at different granular levels, this method optimizes the balance between concurrency and locking overhead. ==Key Concepts== *'''Lock Granularity:''' Refers to the size of the data item on which a lock is appl...") | ||||
| 새글 05:34 | Phantom Record 차이역사 +4,455 Betripping 토론 기여 (Created page with "'''Phantom Record''' refers to a data entry that appears in a dataset but does not correspond to a real-world entity or valid data point. Phantom records can occur due to system errors, data corruption, improper database handling, or intentional insertion during testing or attacks. ==Causes of Phantom Records== Phantom records can arise from various sources: *'''Data Entry Errors:''' Manual input mistakes resulting in duplicate or incorrect records. *'''System Errors:'''...") | ||||
