Hi, I am building an app that will likely become extensive. Therefore, I did not want to clutter up the “user” table with potentially 100 different saved settings, or profile data.
(All kinds of user settings to customize the app and behavior, but nothing that really belongs to another type like products, or events etc. and should go there)
The idea now is to create a separate “User Settings” and “User Profile” type / object (1 to 1) at the user creation event to store all settings data in a settings object, etc.
-
My question is, is that something that would be an efficient approach?
-
And I am also wondering how to access these types in a good and lean way within a workflow, e.g. if I want to switch “Newsletter” from “no” to “yes” for the “currentuser”, if it is stored in a connected “User Settings” object. (The relation is that the “User Settings” object, of which there will be only one per user, has a “Parent User” field, that points to the user the settings are for.)
Thanks for your input, I want to do it right, to reverse something like this would be a significant hassle, later on, I imagine 
