In this tutorial we will get some further experience in developing ER diagrams, and then translate

these to SQL DDL Statements.

Consider the following brief scenario

EliteVideo is a startup company providing concierge DVD kiosk service in upscale

neighbourhoods. EliteVideo can own several copies $($VIDEO$)$ of each movie $($MOVIE$).$ For

example, a kiosk may have $10$ copies of the movie Twist in the Wind. In the database, Twist in the

Wind would be one MOVIE, and each copy would be a VIDEO. A rental transaction $($RENTAL$)$

involves one or more videos being rented to a member $($MEMBERSHIP$).$ A video can be rented

many times over its lifetime; therefore, there is an M:N relationship between RENTAL and VIDEO.

$($DETAILRENTAL$)$ is the bridge table to resolve this relationship. The pricing structure is such that

there are a number of price categories, such as 'Overnight', $\text{'}2$ Day Rental', $\text{'}3$ Day Rental', 'Weekly'

etc. The cost of renting each MOVIE will fall into one of these $($PRICE$)$ categories.

Task $5$

In PostgreSQL and DBeaver, create the new database $($call it MovieDB, prefixed by your

Student ID number$),$ as we did in the first tutorial, and create a new DBeaver connection to

this new database.

Canyou actually create a new database in PostgreSQL and Dbeaver?