0% found this document useful (0 votes)
52 views1 page

Social Media SQL Database

The document describes the requirements for creating a database and entity relationship diagram (ERD) to model a social network system. The database must store user information like name, date of birth, email, as well as posts and friend relationships between users. Users can post statuses that are saved with title, content, and date. The friendship relationship between users needs to track when users became friends and the current status of the friendship. The database and ERD can be designed based on examples from lessons on primary and foreign keys.

Uploaded by

inmmc life
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
52 views1 page

Social Media SQL Database

The document describes the requirements for creating a database and entity relationship diagram (ERD) to model a social network system. The database must store user information like name, date of birth, email, as well as posts and friend relationships between users. Users can post statuses that are saved with title, content, and date. The friendship relationship between users needs to track when users became friends and the current status of the friendship. The database and ERD can be designed based on examples from lessons on primary and foreign keys.

Uploaded by

inmmc life
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Create a database for a system using existing social networks as a model.

The system must have user


information as well as information about the posts they publish. For users, the following information
must be saved:

first name;

name;

date of birth;

place of birth;

email address;

username;

a short CV;

a photo.

For statuses / statuses, the information about the title, content and date of publication of the status
must be stored, so the respective status must also be marked.

Users can become friends, an activity that, of course, needs to be noted somewhere. We must also save
the user who is our user's friend, when they became friends and what is the state of friendship (pending,
accepted, rejected).

To help with this assignment, you can use the example of a relationship in Lesson 2.3. - Primary and
foreign keys.

A database must be created for such a system, but you must also create the EER diagram of entities and
relationships. It doesn't matter if you start with a model and then create a database or vice versa, but it
is certainly recommended to create a model first, because it is more realistic to first create a plan
(sketch, respectively a model) and then transform that model in a real database.

Send the base as a script (.sql) and the model as a .jpg or .png image together in a .zip archive.

You might also like