I am wondering what is the best way to store user settings? For a Web 2.0 application, I want users to be able to choose specific settings. At the moment, this is only when to receive email notifications.
The easiest way is to simply create a “Settings” model and have a column for each parameter, and then have a 1-1 relationship with users.
But is there a sample to solve this better? Maybe it's better to store information in the user table itself? Or should I use a table with the parameters "settings_name" and "settings_value" to fully open the type of settings stored there (without the need to perform any migrations when adding options)?
What is your opinion?
thank
ruby-on-rails settings user-controls
Ole Spaarmann Nov 05 '09 at 17:06 2009-11-05 17:06
source share