3 ms·
Totally agree. I only use Postgres on my stuff now (MySQL in a pinch if there's legacy reasons). I got burned too many times by ORMs. The other point is that t
by marcus_holmes 8y ago
Totally agree. I only use Postgres on my stuff now (MySQL in a pinch if there's legacy reasons). I got burned too many times by ORMs.
The other point is that the data is the most important part of the application in most cases. Understanding how the data fits together, how it's structured and stored, and how to make sure it doesn't corrupt, is one of the key tasks in creating a system. ORMs don't help with this, but SQL forces us to think about the data. Which is good. I can't count the number of bad architectural structures that seemed like a good idea at the time but that I've had to discard (thankfully in the end) because the database told me they wouldn't work.