No, it's a users choice to use a DB that has this tradeoff.
Like it was said a couple of time already, all of your complaints about C* would work just as well for locking mechanisms in most popular languages.
Like it was said a couple of time already, all of your complaints about C* would work just as well for locking mechanisms in most popular languages.
If I can't see the child, should I continue to give them direction, or tell them to stop?
In this use case, the database makes changes to data without knowing what is correct and what is harmful. That is not the user's fault. It's a code choice.