No. I was directly pointed to the quote. Because is a common narrative "if you have problems in a RDBMs, get out of a RDBMS and use nosql".

The previous post kinda say the same, but is weird because call the quote great?

> No.

Yes.

You replied to my reply, where I used addresses as an example. I totally agree with you in general, i.e. use RDBMS as much as possible, but when it's no longer possible - what would you do in the case of addresses?

The big problem with addresses and all that is the same whatever you use JSON or not (in the DB or in the app logic). I concede that using JSON in the DB and move the logic to the App is ok and in part because SQL is an incomplete language.

But that is orthogonal to move out completely to a nosql. That is going too far (in this case).