Refer to the address, store, staff, and customer tables of the Sakila database. In this lab, these tables initially have the same columns as in Sakila, however some constraints are different.

The customer and staff tables have many common columns. Move these columns to a new supertype table person, as shown in the following diagram:

The diagram has five entities and two relationships. The entities are person, staff, customer, address, and store. Person is a super type entity, with subtypes staff and customer. Staff appears above customer, within person. Address and store appear outside person. Person has attributes person$\_$id R U$,$ first$\_$name, last$\_$name, email, active, and last$\_$update. Staff has attributes person$\_$id R U$,$ picture, username, and password. Customer has attributes person$\_$id R U and create$\_$date. Address and store have no attributes. Relationship address$-$belongs$\_$to$-$person has cardinality one$-$many maximum and one$-$zero minimum. Relationship staff$-$works$\_$at$-$store has cardinality many$-$one maximum and zero$-$one minimum.

Follow Sakila conventions for table and column names:

All lower case

Underscore separator between root and suffix

Foreign keys have the same name as referenced primary key

Implement the diagram in three steps:

Step $1.$ Create a person supertype table:

Create a primary key person$\_$id with data type SMALLINT UNSIGNED.

Add the common columns of customer and staff $($refer to the diagram$).$ Specify the same data types and constraints as in customer and staff.

Implement the belongs$\_$to relationship as a foreign key constraint on address$\_$id$.$ Specify the same foreign key rules as in customer and staff.