database - 'Followers' and efficiency -
I am preparing an app that will include users 'following' each other's activity, in twitter sense, but I am not much experienced with database / query design / efficiency, what are the best practices for managing this, etc. to avoid losses? Can I make a huge load on DB if I did not do it properly (or even?).
If it makes a difference, then it is possible that people can only be 'relatively' people (but one person can have many followers), although this is not definite, and I do not trust him Would like to
Thank you received gratitude by any advice.
Easy and easy to complete. If you have a user's table, with each unique ID, you have a TABLE_FOLLOWERS
table with the column, USERID
and FOLLOWERID
For each user, describe all followers as one from one to many relationships.
Even with hundreds of assurances on half-decent database servers, it will display good and fast as long as you are using a good database (IE, MS-Access not).
Comments
Post a Comment