The video seems to say that ACID's consistency property requires that the database supports out-of-order updates. I would disagree. If you had a database with a referential integrity constraint, typically they are enforced immediately when the update happens inside the transaction. Say you have a constraint that a parent record must be created before child record. If the user/app tries to create the child first, the update will be rejected. Some ACID databases can defer these constraints until commit time, but that is a special feature and not a prerequisite for ACID in my view.
The video seems to say that ACID's consistency property requires that the database supports out-of-order updates. I would disagree. If you had a database with a referential integrity constraint, typically they are enforced immediately when the update happens inside the transaction. Say you have a constraint that a parent record must be created before child record. If the user/app tries to create the child first, the update will be rejected. Some ACID databases can defer these constraints until commit time, but that is a special feature and not a prerequisite for ACID in my view.
Thanks for the video :).
Can you publish this document ?
i am not able to use get or edit methods ex:csr.get("running",filter) <---this method is not showing help someone help please