I’m trying to make a mini social network mobile app similar to Instagram, but I’m not sure about my database organization; something seems to be lacking, especially with the Posts table.
At first glance, this has a strong odor. Perhaps I’m mistaken, but this appears to be a plain-text password, which is completely incorrect. The column size should correspond to the output size of the hash function, as well as the salt and hash parameters (or split those into separate columns). Don’t even consider SHA1 or MD5:P For this, use PBKDF2, bcrypt, or scrypt. A more in-depth discussion of password hashing can be found here.
This style is very specific for most western titles, but it is incorrect in general. People’s names in certain parts of the world do not fit into the first/last name format, so a single, longer column is usually sufficient. For more details, read this post.
In general, this is a poor practice because it leads to duplicated and inaccurate data, as well as complicated city/country searches (as anyone can write it the way he wants). A better solution is to divide this into different tables for cities, states, and nations, with a reference to the city in the users table (a city implying a state and a country):
The ability to monitor and eventually re-contact those who use social media is the primary advantage of linking social media experiences with your database. The benefits of tracking your social media users are numerous. You can do the following:
Recognize and honor your ardent supporters.
Here are a few methods for identifying important patrons and other influential people who are loyal to your organization.
Of course, this must be done on a one-time basis—it isn’t automated and requires some effort. The benefit is that you can adapt your contact to their experiences with your company, making your direct interactions more meaningful. My coworkers and I place a high value on devoting this time and effort to cultivating patron loyalty. The payoff, according to our ongoing study of patron activity, is those patrons’ higher lifetime investments in your company.
Increase the efficiency of direct marketing strategies by incorporating social media.
Direct and targeted marketing strategies are the most effective; they present the right offer to the right person at the right time.
For conventional channels like mail, telemarketing, and even email, tracking ROI on direct marketing—for example, through response reporting—is a well-established practice.
Social networking messages are usually stored separately from the database of most organisations.
Connecting the two could be extremely effective, particularly if you have a large social media following with individual interactions.
In the social networking industry, databases are particularly relevant. This industry has an enormous amount of data; nearly 3 billion people use social networking sites every month, and the number is growing. Each of those 3 billion users leaves virtual traces on the network, requiring storage and organization. Each profile, article, like, share, and other piece of information is a new piece of data to be saved.
To manage this amount of data, databases must be updated. Without proper data organization and storage, social media organizations cannot operate. For user engagement, ad targeting, and other business purposes, data must be easily retrievable.
Create a design environment in which developers feel free to experiment. Encourage brainstorming and creativity on a regular basis. Avoid putting too much focus on immediate outcomes at the expense of potential requirements. Build out database features even if you don’t need them right now if there’s a decent chance they’ll support your company in the future.
In this part, we’ll create the User Friend Table, which will be used to store user friends. Friendship status can be tracked using friend status, and friendship form can be used to determine the type of friendship. The descriptions of all the columns in the User Friend Table are listed below.
In this part, we’ll create the User Follower Table, which will be used to store user followers. The follower class may be used to designate the type of follower, which can be one of three options: Like, Dislike, or Follow. The definitions of all the columns in the User Follower Table are described below.
In this part, we’ll create the User Post Table, which will be used to store user posts. Other users with sufficient permissions can be needed to allow the sender to post on the user wall. The definitions of all the columns in the User Post Table are described below.
In this part, we’ll create the Group Member Table, which will be used to keep track of the members of the group. The member position can be used to define the member rights and the member status can be used to monitor the membership status. The following is a list of all the columns in the Group Member Table.