What's the best?
Use a profile table (such as country, age, etc.), or customize a subscription to store information that is not present in the membership table?
Thanks
Membership data should generally include information which Related to authentication I.e. security.
The profile is usually the appropriate place to store user meta data. I.e. privatization.
These 2 types of data serve different purposes and enable a clear separation of concerns in the isolation providers.
An exception to this is if a non-standard meta data is directly related to authentication / authorization.
Whenever possible, it is best to use in the construction of providers. This reduces the amount of code you design, implement, test, and maintain. And membership, i.e. security, is not something you want to find bugs.
Therefore, I will try to try, test and use the true membership provider, and if you want a table based meta, then use the custom profile provider such as
Comments
Post a Comment