For an SN site should there be a Profile model A user’s gotta have a profile I guess right? Then who should pictures belong to, the user or the user’s profile?
Can you give us a clue as to which meaning of SN you are using? SN - Wikipedia does not seem to offer anything that looks particularly likely.
Colin
Social Networking
> For an SN site should there be a Profile model A user's gotta have a > profile > I guess right? Then who should pictures belong to, the user or the > user's > profile?
Can you give us a clue as to which meaning of SN you are using? SN - Wikipedia does not seem to offer anything that looks particularly likely.
Colin
Social Networking
What is in the users table and what is in the profiles table? You might want to combine them into one table. Why make things complicated unless there is a good reason?
If you do have separate tables then the question as to whether the pictures belong to the profile or the user is just a matter of how you wish to organise it. Think about the problem in real world terms. Would the actual user think of the pictures as being his, or would he think that they are the property of his profile?
Colin
That’s what I’m gonna do Originally the purpose of the profiles was for personals since users could have many I was driven by the challenge more than the reality After I did just about the whole site I decided I don’t like this, and I’m scrapping the profile model because first I don’t want users to be able to have multiple personas
The most common mistake in rails apps is creating a user object that does way too much. People call it “the God object”. Just because a user only has one profile doesn’t mean you need to combine those models.
