Roughly I don't think there might be 100% use cases since the features make up the entire hundred 100%. Both are using 2/3 of that, which by the theory that is the maximum adoption.
You should be asking why you nee a nosql database instead. Consistency, atomicity, and transactions are very helpful in writing reliable applications. With nosql you generally have to handle multi document transactions yourself. They don't support aggregations over multiple collections/tables so reporting is a huge pain compared to SQL. SQL should be the default for most applications, unless they have a great motivation to use a nosql database.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What would be real clear examples where I 100% need to use a SQL database versus NoSQL?
Roughly I don't think there might be 100% use cases since the features make up the entire hundred 100%. Both are using 2/3 of that, which by the theory that is the maximum adoption.
You should be asking why you nee a nosql database instead. Consistency, atomicity, and transactions are very helpful in writing reliable applications. With nosql you generally have to handle multi document transactions yourself. They don't support aggregations over multiple collections/tables so reporting is a huge pain compared to SQL. SQL should be the default for most applications, unless they have a great motivation to use a nosql database.