DBers, I am creating a preferences/settings table for a project. Assuming this project will eventually have millions of users and possibly 50-100 preferences per user, what is the best practice for storing this in an RDBMS?
I have seen that WordPress does a combination of more rows and serialized data. I have seen some database tables that have 100+ fields, one for each option. Then there is the table with a handful of fields and then a row of data for each option. If there are 100 users and 100 options that means and easy 10,000 rows. Then again, serializing the data makes the database less cumbersome, but puts the parsing work into the app. Another possibility is grouping the options into multiple tables. Thoughts? Thank you, Jonathan Duncan _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
