Create Skills, User Skills, Interest, User Interest Table

[Caleb-Cohen]

Related Issues Project: Filtering Depends on: N/A

Description

• Utilize sequelize to create the Skills, User Skills, Interest and User Insterest model
• Skills table should have two attributes: skill_id which is an integer and skill_name which is a string.
• User Skills table should have two attributes: user_id which is an integer and skill_id which is an integer.
• Interest table should have interest_id which is an integer and interest_name which is a string.
• User Interest table should have two attributes: user_id which is an integer and interest_id which is an integer.

New table: Skills Table

Column	Type	Notes
skill_id	int	primary key
skill_name	string	individual skill traits

New table: User Skills Table Column	Type	Notes
user_id	int	primary key of user table (Foreign Key)
skill_id	int	primary key of skills table (Foreign Key)

New table: Interest Table Column	Type	Notes
interest_id	int	primary key
interest_name	string	individual interest of user

New table: User Interest Table Column	Type	Notes
user _id	int	primary key of user table (Foreign Key)
interest_id	int	primary key of interest table (Foreign Key)

Acceptance Criteria

• DB Tables Skills, User Skills, Interest, User Interest table exists
• models exist in server/model

[jmoldyvan]

I'm all over this when it's not a draft!

[jmoldyvan]

You don't mention the attributes for the user interest table, is that in the tech spec or would it just be a blank table?

[timmyichen]

Nit: Running the migration isn't really necessary to call out - in order to test it locally, they'll need to run migrations, and in production (staging), they're run automatically. Otherwise I think it'd be helpful to include the tables (can just be copy-pasted) from the tech spec. Be sure to include any foreign key relationships.

I'd also include as part of the AC that the models exist in the server/models folder

[Caleb-Cohen]

You don't mention the attributes for the user interest table, is that in the tech spec or would it just be a blank table?

Updated

Nit: Running the migration isn't really necessary to call out - in order to test it locally, they'll need to run migrations, and in production (staging), they're run automatically. Otherwise I think it'd be helpful to include the tables (can just be copy-pasted) from the tech spec. Be sure to include any foreign key relationships.

I'd also include as part of the AC that the models exist in the server/models folder

Updated