Timeline for Help me design this use case
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 24, 2015 at 11:46 | comment | added | Philipp | @MangatRaiModi What's a "column" and a "table"? Such things do not exist in MongoDB. Or do you mean field and collection? Like with every database system, each additional index reduces performance for inserts and for any updates which affect the indexed fields. Also, indexes require additional storage space. You might consider to turn those 100 fields into an array of objects where the field-name is the value of a key. Or not - it depends on how you query your data and how many datasets you expect per document. | |
| Jul 24, 2015 at 11:43 | comment | added | Mangat Rai Modi | How will MongoDB perform if I have index on all the columns(100) in the table? As I need reverse query for each of them. Same index will work on sub categories also? @Negative Voter, I am not familiar with MongoDB could you please point out the problem with this answer? | |
| Jul 23, 2015 at 12:33 | history | edited | Philipp | CC BY-SA 3.0 |
deleted 1 character in body
|
| Jul 23, 2015 at 11:50 | history | answered | Philipp | CC BY-SA 3.0 |