I don't think I'm very anti-ORM, but I prefer using SQL where I feel for it. ORM is usually an overhead, and a bad implementation can make the ORM useless. To

I don't think I'm very anti-ORM, but I prefer using SQL where I feel for it. ORM is usually an overhead, and a bad implementation can make the ORM useless. To answer your question: do we need to learn a QRM now? :) I think we are a few years away from that, ref. "what was the average salary for people earning more than X USD in 2019, adjusted for the purchasing power each person lives in?" This is an example of a third-party data set that you don't want to be part of your core application, but maybe for a reporting system that talks to both your core application and some other third-party sources. So. I'll stay with SQL until further notice, because a) this doesn't work, and b) third party data needs careful handling.