Vertaile menetelmiä
Tarkastele valitsemiasi menetelmiä rinnakkain; eroavat rivit korostetaan.
| Transaktioiden hallinta× | Rinnakkaisuusohjaus× | |
|---|---|---|
| Tieteenala | Tietojärjestelmätiede | Tietojärjestelmätiede |
| Menetelmäperhe | Process / pipeline | Process / pipeline |
| Syntyvuosi≠ | 1981 | 1978 |
| Kehittäjä≠ | Jim Gray and others (IBM) | Jim Gray and David Reed |
| Tyyppi≠ | Database reliability mechanism | Database coordination mechanism |
| Alkuperäislähde | Gray, J. (1981). The transaction concept: Virtues and limitations. VLDB Endowment, 7(6), 519-539. link ↗ | Gray, J. (1981). The transaction concept: Virtues and limitations. VLDB Endowment, 7(6), 519-539. link ↗ |
| Rinnakkaisnimet | ACID transactions, transaction control | locking, MVCC |
| Liittyvät | 1 | 1 |
| Tiivistelmä≠ | Transaction management is the mechanism by which database systems ensure reliable execution of multiple interdependent operations as atomic units. Formalized by Jim Gray and colleagues in the 1980s, transactions guarantee ACID properties (Atomicity, Consistency, Isolation, Durability) that protect data integrity even in the face of failures and concurrent access. | Concurrency control is the set of mechanisms used to coordinate concurrent transactions accessing shared data without corrupting the database. Formalized by database theorists in the 1970s-1980s, concurrency control ensures that multiple simultaneous transactions produce the same result as if they executed sequentially (serializability). |
| ScholarGateAineisto ↗ |
|
|