New answers tagged database-structure
I wouldn't suggest using capped collections: they scale badly, as they can't be sharded as of the time of this writing and maybe never. See the according feature request on MongoDB's JIRA. I would use a different approach. Use the users query string as _id. Since the exact query is what identifies your records, there is no need to hash it on the client ...
In addition to what @jynus has written above - check out my answer to a similar question here (see reference to Celko). Furthermore, the MySQL ENUM type should be avoided for many reasons - 8 reasons as to why they are "evil" can be found here.
I recommend you to read about the dangers of the Entity-Attribute-Value pattern on this presentation by @Bill Karwin. One of the solutions is storing NoSQL-like data in a serialized BLOB, if you do not need to read and write individual properties. That is, storing a key (product) as the primary key, and the variable property-value pairs all together in a ...
Top 50 recent answers are included