test

Users

Table needed to store all data related with users. And this table contains:

• id – unique key
• name – first and last name of user
• login – login(nickname) of user
• bio – a brief description about yourself
• email – email of user
• password – hashed password of user
• country – country of user
• city – city of user
• phone – user's mobile number of phone
• role – role of user in the platform

Followers

Since users can subscribe to each other it is logical to keep the followers in this table. Table Followers consist of:

• id – unique key
• user_id – unique key for table Users, needed to bind tables
• follower_id – unique key for user(follower), needed to bind table

Notification

Users can receive notifications about different events. All of this notifications saved in table Notification. This table contains:

• id – unique key
• user_id – unique key for table Users, needed to bind tables
• type – type of notifications(can be followed, updated etc.)
• message – message which to inform user what happens

Skills

Skills is the main entity on the platform. Because all data of skills stores in table Skills. This table contains of:

• id – unique key
• title – name of skill
• image – link to image which related with skill
• description – a brief description of the skill(technology)

Users_Skills

This is intermediate table which bind tables Users and Skills. Table consist of:

• id – unique key
• user_id – unique key for table Users, needed to bind tables
• skill_id – unique key for table Skills, needed to bind tables

Vacancy_Number

The table contains the count of vacancies for a certain period of time. This table have next fields:

• id – unique key
• skill_id – unique key for table Skills, needed to bind tables
• last_count_vacancy – count of vacancies for skill