Discuss these questions with your fellow table mates and try to model some solutions to the questions
1 . What would a Users table look like? What columns do you think would be in the table?
2 . As a user you should be able to look at a list of movies and select any individual movies to add to your Queue. How would you model the relationship between a User and their Queue of Movies? What kind of properties would a Queue have? What kind of relationships would a Queue have with other tables? Be sure to be very clear about on which table(s) the foreign keys are found. Be sure your domain allows the same Movie to appear on many different user's queues
3 . A Movie has a plot, title, rating, duration, actors/actresses, and reviews. How would you model each of these relationships with a Movie? What would would you call the relationship between an Actor and a Movie?
4 . As a user you should be able to leave a Review on a Movie. Would a Review be a property of a User or its own table? Why? If a Reviewer does not have a direct relationship to a Movie, how can a Movie list the names of its Reviewers? What would you call this relationship?
View Domain Modelling on Learn.co and start learning to code for free.