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.

Implement a new strong entity phone, as shown in the following diagram:

The diagram has four entities and three relationships. The entities are phone, store, staff, and customer. Phone has attributes phone$\_$id R U$,$ country$\_$code R$,$ phone$\_$number R$,$ and phone$\_$type. Store, staff, and customer have no attributes. The relationships are store$-$has$-$phone, staff$-$has$-$phone, and customer$-$has$-$phone. All relationships have cardinality one$-$one maximum and zero$-$zero minimum.

The diagram uses Sakila naming conventions. Follow the Sakila conventions for your 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.$ Remove the phone column from address. This column is replaced by the new strong entity.

Step $2.$ Implement the strong entity as a new phone table. Specify data types VARCHAR$(12)$ for phone$\_$type and integer for other columns. Specify a suitable primary key and NOT NULL constraints according to the diagram.

Step $3.$ Implement the has relationships as foreign keys in customer, staff, and store. Specify UNIQUE constraints according to the diagram. Specify SET NULL for delete rules and CASCADE for update rules, as follows:

ALTER TABLE customer

ADD FOREIGN KEY $($phone$\_$id$)$ REFERENCES phone$($phone$\_$id$)$ ON DELETE SET NULL ON UPDATE CASCADE;