in reply to Storable for user preferences

Storable is fine but it isn't clear to me what the benefits would be here. I would go with EAV: stick with the database but have a preferences table which consists of a user ID, a preference name and a preference value. When you query the preferences table for a combination of user and preference name and there is no matching row then you can use the system-wide default value. Why would this not be simple/efficient?


🦛