That's similar to what I currently have set up. The problem is it is a request based system.
Example table: id1 id2 group flag When a person makes a request something such as the following is insert: MYID, REQUEST_USER_ID, 'family', 0 If user REQUEST_USER_ID accepts it will be flagged as 1: MYID, REQUEST_USER_ID, 'family', 1 Using 2 tables would help the indexing problem, but it's definetly NOT how I want to achieve this. -----Original Message----- From: Jad madi [mailto:[EMAIL PROTECTED] Sent: 07 April 2006 15:00 To: Martin Gallagher Cc: mysql@lists.mysql.com Subject: Re: Social Network, linking members How about something like this Users table user_id user_name user_password user_whatever and then Relation table rel_id user_id friend_id and then selecting from relations table On Fri, 2006-04-07 at 14:47 -0700, Martin Gallagher wrote: > urrently I link them using 2 separate fields for the members: id1, > id2. So, -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
