- Atomic (if the change is committed, it happens in one fell swoop; you can never see “half a change”)
- Consistent (the change can only happen if the new state of the system will be valid; any attempt to commit an invalid change will fail, leaving the system in its previous valid state)
- Isolated (no-one else sees any part of the transaction until it’s committed)
- Durable (once the change has happened – if the system says the transaction has been committed, the client doesn’t need to worry about “flushing” the system to make the change “stick”)
See the Wikipedia ACID entry for more details.
Although this is typically applied to databases, it doesn’t have to be. (In particular, see Software Transactional Memory.)
Original: https://www.cnblogs.com/kungfupanda/p/16474053.html
Author: 功夫 熊猫
Title: What is a database transaction?
原创文章受到原创版权保护。转载请注明出处：https://www.johngo689.com/552377/
转载文章受原作者版权保护。转载请注明原作者出处！