3 ms·
I actually wouldn't say this is very controversial, ORM is a problem that (in some ways) is fundamentally intractable. There is some great reading on this subj
by CitizenKane 17y ago
I actually wouldn't say this is very controversial, ORM is a problem that (in some ways) is fundamentally intractable. There is some great reading on this subject with an article titled "The Vietnam of Computer Science" (http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Computer+Science.aspx http://blogs.tedneward.com/2006/06/26/The+Vietnam+Of+Compute...). This was pretty eye opening for me and I think it's a must read for any web developer (or anyone using ORM for that matter).
- steveklabnik 17y agoThanks for posting this. I came to the ORM party a little late, and am still pretty infatuated with them overall. I was thinking when I saw the link that I've never had a problem with an ORM, but then realized two things: 1) I've only ever used them with fresh projects, where I had control over everything 2) I designed my objects with the ORM in mind. I'd only ever bumped up against annoyance with an ORM when I was trying to do something with inheretance, and after a brief check into Rails' 'polymorphic relationships,' the requirement was basically dropped anyway. Hm.