 |
|
|
|
|
|
|
|
|
|
|
|
| l |
Classic: system crash between one bank account being
debited and
|
|
|
|
another being
credited.
|
|
|
| l |
Dramatic:
power failure during update
statement on 3 million rows
|
|
|
after 2 minutes
when only part way through.
|
|
|
| l |
Real-world:
complex series of
inter-related updates, deletes and
|
|
|
|
inserts on many
separate tables fails at the last step due to a
|
|
|
|
duplicate primary
key on an insert.
|
|
|
| l |
Transaction
recovery would handle all these situations automatically.
|
|
| l |
Makes a system
far more robust and trustworthy
over the long term.
|
|
|
| l |
Use transactions
if your database supports them.
|
|
|
| l |
If it doesn't and
you need them, switch to a different database.
|
|