As a User, I'd like my preferences to be tracked, such as my preferred language

[robyurkowski]

So if I prefer to view the site's French side, whenever I log in, it should always display in French to me.

[parndt]

So, all users require a discrete settings store, somehow.

[knewter]

So then you have the question of how to handle this settings store. Arbitrary key/value stores are cool but obviously the persistence strategy has issues. If you never want to query against them, serializing makes sense, and then in postgres you can take advantage of HStore so that you can index in that case if you need to.

HEY GUYS I THINK WE NEED MONGODB

[robyurkowski]

Hstore is wicked cool, but do we want to advise that this has to be run on Postgres? I don't think we can do that, and I don't even think that having 'additional' functionality is necessarily something great.

In my mind, this is as simple as creating Abc::UserProfile, 1:1-ing this with the user class, and delegating to profile certain things.

As cool as k/v stores are, this isn't exactly the sort of data that's so irregular to be unsuited to standard SQL tables.