Backing Up File Versions with File History
High-end databases have long supported the idea of the transaction, a collection of data modifications—inserts, deletions, updates, and so on—treated as a unit, meaning that either all the modifications occur or none of them does. For example, consider a finance database system that needs to perform a single chore: transfer a specified amount of money from one account to another. This involves two discrete steps (I’m simplifying here): debit one account by the specified amount and credit the other account for the same amount. If the database system did not treat these two steps as a single transaction, you could run into problems. For example, if the system successfully debited the first account but ...
Get Windows 8 In Depth now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
