3 ms·
It seems like this stackoverflow question hits on the same issue you ran into.[1] It looks like that might be specific to Firebase's implementation because thi
by jklein11 9y ago
It seems like this stackoverflow question hits on the same issue you ran into.[1]
It looks like that might be specific to Firebase's implementation because this can be achieved with Mongodb.[2]
1. https://stackoverflow.com/questions/27207059/firebase-query-double-nested https://stackoverflow.com/questions/27207059/firebase-query-...
2.https://stackoverflow.com/questions/15654228/sort-by-embedded-document https://stackoverflow.com/questions/15654228/sort-by-embedde...
- dahart 9y agoNo, that's not the issue I ran into. Their API has changed since this question was asked & answered to fix that particular issue. The bigger issue remains that schema nesting causes a type of complexity that SQL dbs avoid by always being flat. Even that answer you linked to, the very last sentence is: the most important one for people new to NoSQL/hierarchical databases seems to be "avoid building nests". Schema nesting in mongodb is also best avoided, if you can, e.g.: https://stackoverflow.com/questions/5108790/mongodb-best-practice-nesting https://stackoverflow.com/questions/5108790/mongodb-best-pra...