4 ms·
I think there may be an error in part 2 of this guide where it talks about ACID. To my understanding, the C (Consistency) in ACID is referring to the structure
by nfw2 4y ago
I think there may be an error in part 2 of this guide where it talks about ACID.
To my understanding, the C (Consistency) in ACID is referring to the structure of the database. In other words, a SQL table can't be updated in such a way that violates the column definitions and constraints defined by the table.
In this guide, it seems to be talking about strong consistency vs eventual consistency when discussing ACID, which, to my understanding, is a different topic entirely, and refers to the timeliness of accurate reads.
- layer8 4y agoYes. The Consistency property means that at the end of every transaction, the resulting data state in the DB will be consistent with the schema definition, including any constraints, triggers, etc. In other words, no transaction will result in invalid data with respect to the schema definition. This is similar to soundness in programming languages.
- layer8 4y agoTo add: Strong vs. weak/eventual consistency is more related to the Isolation property of ACID.