Microsoft SQL Server
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
 
User Name:
Password:
Remember me
 
Go Back   Dev Articles Community ForumsDatabasesMicrosoft SQL Server

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Display Modes
 
Unread Dev Articles Community Forums Sponsor:
  #1  
Old May 3rd, 2007, 01:27 AM
shylender shylender is offline
Registered User
Dev Articles Newbie (0 - 499 posts)
 
Join Date: May 2007
Posts: 1 shylender User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 9 m 10 sec
Reputation Power: 0
Doubt on Social Networking Program

We are developing social networking project. we have to create different communities for Site. My question is whether we have to create seperate tables for different communities. Please help me.

Reply With Quote
  #2  
Old May 23rd, 2007, 08:13 AM
JDNichols JDNichols is offline
Registered User
Dev Articles Newbie (0 - 499 posts)
 
Join Date: May 2007
Posts: 1 JDNichols User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 27 m 28 sec
Reputation Power: 0
Quote:
Originally Posted by shylender
We are developing social networking project. we have to create different communities for Site. My question is whether we have to create seperate tables for different communities. Please help me.


Not always. It depends more on your overall relational model for your database.

Although if I was doing it...I would probably make a table which contained the following:

Community ID - Unique Identifier (Primary Key)
Community Name - The name of this particular community

Also add in any other relevant columns for information about the each community.

Then I would have another table which would be used as a bridge between your Users and your Communities tables. It would look something like:

Community ID - The ID of the community the User is in.
User ID - The ID of that particular user

Put together this would make a composite primary key and it would keep track of all users and any communities they are a part of (example: one record could be User ID 1, Com ID 1, while another record could have User ID 1, Com ID 4, and another user record could be User ID 3, Com ID 1. This would show that User ID 1 is in Communities 1 and 4, and User ID 3 is in Group 1).

Again, this is entirely dependent on your overall database design, but it is more than likely the most appropriate route for keeping track of communities and what users are in them.

Reply With Quote
Reply

Viewing: Dev Articles Community ForumsDatabasesMicrosoft SQL Server > Doubt on Social Networking Program


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway
Stay green...Green IT