News for hackers. Stuff that matters.
Re:Don't use MongoDB by bborud on Sunday November 06, 2011 @08:15AM (#3202576)
ORMs are a pain to use. In addition to know the domain you need to map from and the domain you map to, you now also have to understand the mapping process.
Re:Don't use MongoDB by zzzeek on Sunday November 06, 2011 @02:12PM (#3203489)
...in exchange for dramatically pared-down and simplified code, consistent data access practices, and hundreds of hours of developer time saved. Driving a car is tough too - how to steer, drivers license, gas, insurance, what a PITA. Yet somehow it remains preferable to walking in many cases, despite the latter being mastered by most two year olds.
Re:Don't use MongoDB by bborud on Monday November 07, 2011 @01:29PM (#3207522)
If you need all that code to talk to the database I suspect you are in effect using your database as the integration layer. Ouch.
Re:Don't use MongoDB by rapind on Sunday November 06, 2011 @08:30AM (#3202604)
The same should be said for ODMs as well. A document might be a little more straightforward to map to an object but there is still plenty of miss-match.
Re:Don't use MongoDB by latch on Sunday November 06, 2011 @08:45AM (#3202636)
I'll agree with this. Document stores don't solve the object-relational impedance mismatch, but they do help (and personally, I find they help more than "a little").
Re:Don't use MongoDB by einhverfr on Monday November 07, 2011 @12:06AM (#3205076)
ORMs encourage bad database design and little interoperability on the db level.

On short folks build their db around the ORM instead of vice versa.