[x] Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
[x] foreign key and table name are lowercased, snake_cased and back_ticked
[x] Correctly formatted
[X] schema is written in a table format
[x] the table's name are lowercased, snake_cased and back_ticked
[X] the table header column names are bolded
[x] columns names are lowercased and snaked_cased and back_ticked
Comments
We can nix the has_many :jobposts association for our users.
Can comments have a parent_comment_id? Should they? Does LinkedIn allow for this kind of comment threads?
Can you clarify what your connections table stores? Is the conenction_id another user's id? If it is, then does that establish a connection and if it does, then do we want that connection to be unique?
I like that we're aiming for Polymorphic associations for our Likes. We can discuss these later and possibly scale down to just Likes for Posts, depending on our progress. Polymorphism could be a Bonus.
Database Schema
back_ticked
back_ticked
back_ticked
Comments
has_many :jobposts
association for ourusers
.comments
have aparent_comment_id
? Should they? Does LinkedIn allow for this kind of comment threads?connections
table stores? Is theconenction_id
another user'sid
? If it is, then does that establish a connection and if it does, then do we want that connection to be unique?Polymorphic
associations for our Likes. We can discuss these later and possibly scale down to just Likes for Posts, depending on our progress. Polymorphism could be a Bonus.