I would create an abstract class to hold the share values, extend from that
for your n shared fields, use those as OneToOne in your user profile, and
then have methods in the userprofile to determine if the field should be
shown. Something like this (assumes you have the code to figure out if a
I want to implement privacy settings on my extended UserProfile Model where
the user can decide who can see his field (say email for now).
The options looks something like this,
*public* - any one can view his email
*friends_of_friends* - only friends and friends of friends can view his
email
*f
2 matches
Mail list logo