Database schema for social network members table

[eluser]jedd[/eluser]
Fairy nuff. On the table I described, you'd still (of course) need a WHERE clause that allowed for user id in person1 OR person2 .. but the distinction between originating versus target person was necessarily blurred. I haven't done this in a Real Live System before, but am doing similar things with other types of data in my current project.

The naming you used indicated an owner of the relationship - which might be of interest (who established the connection, I mean) though it's probably not a hugely important piece of data to retain for friendly social networks.