A kind of Yelp but for mechanics only: Suppose you are in charge of a community

Question

A kind of Yelp but for mechanics only: Suppose you are in charge of a community website that helps people find auto mechanics in their area. Users may post ratings and reviews of auto mechanics but they need to register first. You want to design a database for this website with the following features:

Each registered user has a unique user name, a first name, last name, address information and e-mail address; however, your public website displays only the user name.  

For each mechanic, you want to store the name, address, phone number, and website URL.

Each review is posted by a single user about a single mechanic, and consists of a service quality rating on a scale of 1 to 5, service cost, and comments.  

Each user may review many mechanics, but is only allowed to make one review per mechanic.

Question: How many tables do you need to design a DB for this situation?

(a) Two tables: USER and REVIEW

Two tables: MECHANIC and USER

Three: MECHANIC, USER, and REVIEW

Four: MECHANIC, USER, REVIEW, and WEBSITE

(a) Two tables: USER and REVIEW

Two tables: MECHANIC and USER

Three: MECHANIC, USER, and REVIEW

Four: MECHANIC, USER, REVIEW, and WEBSITE

Explanation / Answer

Option c

Related Questions

Navigate

• Browse (All)
• Browse A
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.