In this tutorial, we will gain additional experience in creating ER diagrams and subsequently translating these into SQL DDL Statements.

Consider the scenario described below:

EliteVideo is a startup company that offers a concierge DVD kiosk service in upscale neighborhoods. EliteVideo may have multiple copies $($labeled as VIDEO$)$ of each movie $($labeled as MOVIE$).$ For instance, a kiosk could hold $10$ copies of the movie "Twist in the Wind." In our database, "Twist in the Wind" would be classified under one MOVIE entry, and each individual copy would be recorded as a VIDEO. A rental transaction $($RENTAL$)$ involves one or more videos being rented to a member $($MEMBERSHIP$).$ Since a video can be rented numerous times throughout its lifespan, there is an M:N relationship between RENTAL and VIDEO. This relationship is managed through a bridge table named DETAILRENTAL. The pricing model includes various categories such as 'Overnight', $2$ Day Rental', $\text{'}3$ Day Rental', 'Weekly', etc., with each MOVIE falling into one of this pricing $($PRICE$)$ categories.

Task $1$

List the attributes you would expect to find in each of the tables mentioned above