facebook brute force
Database design of social networking?
Using Facebook as an example, each member of a group of "friends." On the basis of data, which has a table with the 'field' MemberID 'and another field friendID? This seems very inefficient in terms of strength and redundant data (ie if the member has 10 friends, which is 10 tickets.) — — Or you could have one entry per member, and a field that could be friendID a string separated by commas or something .. appears to be more effective in the database would increase the processing time to analyze chain. I would choose option 1). Ideas? Opinions? Other options? Thanks in advance. It seems that the two first responders have the choice 1) … alternatives?
Option 1) is the way forward. You need to add restrictions foreign key to ensure consistency.
Facebook Brute Force Tool Created by Me
