Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram:The diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names:All lower caseUnderscore separator between root and suffixForeign keys have the same name as referenced primary keyWrite CREATE TABLE and ALTER TABLE statements that:Implement the entity as a new phone table.Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables.Remove the existing phone column from the Sakila address table.Step 2 requires adding a foreign key constraint to an existing table. Ex:ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone(phone_id) ON DELETE SET NULL ON UPDATE CASCADE;Specify data types as follows:phone_id, phone_number, and country_code have data type INT.phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'.Apply these constraints:NOT NULL constraints correspond to cardinalities on the diagram above.Foreign key actions are SET NULL for delete rules and CASCADE for update rules.Specify a suitable column as the phone table primary key. storestaffcustomer1(0)1(0)1(0)hashashas1(0)phonephone_id 1-1(1)country_code M-1(1)1(0)| phone_number M-1(1)phone_type M-1(0)1(0) y! NBA free age X← → CGmailhttps://portal. XYouTubelearn.zybooks.com/zybook/DAT_380_55841896/chapter/5/section/6University of X zy Section 2.1 - ×Maps=zyBooks My library > DAT/380: Advanced Database Architecture home > 5.6: LAB - Implement independent entity (Sakila)●●MySQL :: My xDeveloping S X5.6 LAB - Implement independent entity (Sakila)Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram:●store417736.1426142.qx3zqy7staffLAB1(0)1(0)customer 1(0)hasHomehas10hasThe diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names:• All lower caseUnderscore separator between root and suffixForeign keys have the same name as referenced primary keyWrite CREATE TABLE and ALTER TABLE statements that:1(0)ALTER TABLE customerADD FOREIGN KEY (phone_id) REFERENCES phone (phone_id)ON DELETE SET NULLON UPDATE CASCADE;Xphonephone_id 1-1(1)country_code M-1(1)1(0) phone_number M-1(1)phone_type M-1(0)1(0)Gradebook1. Implement the entity as a new phone table.2. Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables.3. Remove the existing phone column from the Sakila address table.Step 2 requires adding a foreign key constraint to an existing table. Ex:Specify data types as follows:phone_id, phone_number, and country_code have data type INT.phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'.Apply these constraints:• NOT NULL constraints correspond to cardinalities on the diagram above.Foreign key actions are SET NULL for delete rules and CASCADE for update rules.Specify a suitable column as the phone table primary key.× zy Section 5.6 XNew TabNew TabEzyBooks catalogSearch result X? Help/FAQJasmine Lawless

First check whether phone_id column exists in your customer, staff, and store table or not. If…

5.6 LAB - Implement independent entity (Sakila) Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram: store staff 1(0) 1(0) 4177361426142qzay? has has has phone phone_id 1-1(1) country_code M-1(1) 1(0) phone number M-1(1) phone_type M-1(0) 1(0) 1(0) customer 1(0) 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 Write CREATE TABLE and ALTER TABLE statements that: 1. Implement the entity as a new phone table. 2. Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables. 3. Remove the existing phone column from the Sakila address table. Step 2 requires adding a foreign key constraint to an existing table. Ex: ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone (phone_id) ON DELETE SET NULL ON UPDATE CASCADE; Specify data types as follows: • phone_id, phone number, and country_code have data type INT. • phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'. Apply these constraints: • NOT NULL constraints correspond to cardinalities on the diagram above. • Foreign key actions are SET NULL for delete rules and CASCADE for update rules. • Specify a suitable column as the phone table primary key.

7th Edition

ISBN:9780133594140

Author:James Kurose, Keith Ross

Publisher:James Kurose, Keith Ross

Chapter1: Computer Networks And The Internet

Section: Chapter Questions

Problem R1RQ: What is the difference between a host and an end system? List several different types of end...

Related questions

Question

Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram:

The diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names:

Write CREATE TABLE and ALTER TABLE statements that:

Implement the entity as a new phone table.
Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables.
Remove the existing phone column from the Sakila address table.

Step 2 requires adding a foreign key constraint to an existing table. Ex:

ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone(phone_id) ON DELETE SET NULL ON UPDATE CASCADE;

Specify data types as follows:

phone_id, phone_number, and country_code have data type INT.
phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'.

Apply these constraints: