3 ms·
ORMs seem amazing up until the inevitable point of hitting a performance issue or bug, and having to print the underlying statement. At that point you are no lo
by pantelisk 6y ago
ORMs seem amazing up until the inevitable point of hitting a performance issue or bug, and having to print the underlying statement. At that point you are no longer fighting with the bug impacting your systems, you are fighting with the ORM midddle-ware it self, and having to quickly improve your SQL competency above everything else.
That is the moment you 've lost all the benefits advertised.
For smaller systems it might be ok I guess, but stay alive long enough and you 'll see that sooner or later every small system desires to grow, grow and grow!
- bsaul 6y agothe way to debug performance on a large sql system is to log things on the sql server itself and monitor for weird queries. Tjis is part of monitoring a db and this has to be done no matter which tech you used to generate those queries. good ORMs all have a way to fine-control the underlying statements to avoid querying individual rows one by one. I'm fairly proficient with sql queries and i still don't like writing sql queries and binding to objects manually
- balfirevic 6y ago> That is the moment you 've lost all the benefits advertised. No, that makes no sense. If you have to investigate 2 places where performance issues have cropped up and hand-write the SQL in those places, while 95% of your application works just fine, how did you lose all the benefits? My SQL competency was fine from the beginning, thank you very much.
- deleted 6y ago[deleted]