Quote:
Originally Posted by suzzer99
It sounds like maybe you should be using a relational system. Non-relational DBs are best when you need one record accessed by an ID or a small group of records looked up by a secondary index. In your case I'd probably store the occupation information with the user.
If you need a list of all persons then you probably don't want to us a nosql DB. That doesn't scale.
I am aware of that and it is beyond me why anyone would model relational data using noSQL, but as I mentioned in my previous post, re-writing the schema is really not an option (many documents in a single collection have varying number of properties and other such things that make it difficult to convert). For this reason, it seems easier just to suck it up and do the required queries on the data as it is, but I'm having a hard time understanding how joins work in Mongo.