4 ms·
Using hierarchical data structures takes care of the most common use case of JOIN (i.e. "SELECT * FROM a, b, c"). This is a win for MongoDB. However there are t
by rpedela 13y ago
Using hierarchical data structures takes care of the most common use case of JOIN (i.e. "SELECT * FROM a, b, c"). This is a win for MongoDB. However there are times when you want to JOIN multiple hierarchical data structures [1]. Or use a different type of JOIN.
[1] http://tebros.com/2011/07/using-mongodb-mapreduce-to-join-2-collections/ http://tebros.com/2011/07/using-mongodb-mapreduce-to-join-2-...
- mason55 13y agoSo JOIN in your application. Or use a different DB. MongoDB isn't correct for every use case and they would never claim it is.
- ArbitraryLimits 13y agoAm I just too old for HN now? I can understand calling something that holds your data and makes it so you don't have to do JOINs a database. I can understand calling something that holds your data and does JOINs for you a database. I'm having trouble calling something that holds my data and makes it so I have to "JOIN in my application" anything but a file system.
- untog 13y agoI don't know, what is the definition of a database? I'd be surprised if it mandated joins.
- gaius 13y agoActually, if you speak to them, they do claim that. Then they backtrack when you call them on it, but I've heard guys from 10gen as they were known then claim their product was a drop-in replacement for Oracle.
- omni 13y agoHearsay and strawman arguments don't make for an intellectual discussion.