5 ms·
Where’s the anti-ORM crowd to defeat this idea?
by pokstad 4y ago
Where’s the anti-ORM crowd to defeat this idea?
- pkulak 4y agoThis seems so far in the other direction that the same criticisms no longer apply. It would be like being against LCD screens in cars, and then complaining that Boeing's new 787 has flight displays.
- thatwasunusual 4y agoI 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.
- Quarrelsome 4y agoWhen you can only produce SQL via natural language prompts then how are you going to be able to troubleshoot your queries?
- alberth 4y agoSilly question, but are you suggesting that in code you'd put: sql_ai = "which customer spent the most with us in the past 12 months?";
- yrgulation 4y agoShh dont give them ideas. The PHP crowd will absolutely try to adopt it.