3 ms·
I don't think that's remotely true. People tend to use ORMs for much more superficial reasons like not wanting to manually build SQL query strings (which is val
by stormbrew 13y ago
I don't think that's remotely true. People tend to use ORMs for much more superficial reasons like not wanting to manually build SQL query strings (which is valid, as this is error prone, but I still maintain that it's superficial) or because the environment provides them. I've seen many apps that are extremely well suited for a relational database but function terribly because the ORM doesn't let them get at an actual relational model.
- EGreg 13y agoSo you just proved my point. Just because the ORM is there doesnt mean you have to use it. There are libraries that generate relational SQL without ORM!
- stormbrew 13y agoI don't think so? I agree that just because the ORM is there doesn't mean you have to use it, but where I disagree is the idea that people incorrectly using an ORM means they should be using an object or document database. They should use a tool suited to their job, but often they're using an ORM because it's been presented to them as a path of least resistance and a silver bullet. You can't tell anything about what tool is appropriate for the job they're trying to do from their lack of investigation.