I have a SaaS application, where accounts want to save different types of information on a User model. So for example, one account may want to save age, and birthdate, but in another account, they won't be using those columns and will want to save info on hair color, and height.
These are just examples, but how would I structure my model and db so that it works well with "customized, dynamic" columns without creating too many empty attributes.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…