1. Modifying a Relational Database Scheme Recall this database schema from class, which could be used to keep track of orders from customers. Recall that boldface indicates a primary key. Also recall that a line marked by infinity indicates a foreign key whose corresponding column is indicated by the field linked by that line. Products 1818 Order Details Order ProductID UnitPrice Quantity Discount Customers Customer CompanyName ContactName ContactTitle Address City Region PostalCode Country 00 Orders Order CustomerID EmployeeID Order Date RequiredDate ShippedDate Ship Via Freight ShipName ShipAddress Ship City ShipRegion ShipPostalCode Ship Country DO ProductID Product Name Supplier ID CategoryID QuantityPerUnit UnitPrice UnitsInStock UnitsOnOrder ReorderLevel Discontinued Categories Category CategoryName Description Suppliers Supplier CompanyName Contact Name ContactTitle Address City Region PostalCode Country Phone Fax HomePage Phone Fax Shippers Shipper CompanyName Phone Employees Employee LastName FirstName Title TitleOfCourtesy BirthDate HireDate Address City Region Postal Code Country HomePhone Extension Photo Notes Reports To Describe how you would change this schema to keep track of multiple addresses for each customer. Your solution should allow a customer to have any number of addresses. Draw the portion of the schema that you are changing. Underline the primary key in any table you change, and clearly indicate any foreign keys with a line and the correct "1" and "infinity" labels. 1. Modifying a Relational Database Scheme Recall this database schema from class, which could be used to keep track of orders from customers. Recall that boldface indicates a primary key. Also recall that a line marked by infinity indicates a foreign key whose corresponding column is indicated by the field linked by that line. Products 1818 Order Details Order ProductID UnitPrice Quantity Discount Customers Customer CompanyName ContactName ContactTitle Address City Region PostalCode Country 00 Orders Order CustomerID EmployeeID Order Date RequiredDate ShippedDate Ship Via Freight ShipName ShipAddress Ship City ShipRegion ShipPostalCode Ship Country DO ProductID Product Name Supplier ID CategoryID QuantityPerUnit UnitPrice UnitsInStock UnitsOnOrder ReorderLevel Discontinued Categories Category CategoryName Description Suppliers Supplier CompanyName Contact Name ContactTitle Address City Region PostalCode Country Phone Fax HomePage Phone Fax Shippers Shipper CompanyName Phone Employees Employee LastName FirstName Title TitleOfCourtesy BirthDate HireDate Address City Region Postal Code Country HomePhone Extension Photo Notes Reports To Describe how you would change this schema to keep track of multiple addresses for each customer. Your solution should allow a customer to have any number of addresses. Draw the portion of the schema that you are changing. Underline the primary key in any table you change, and clearly indicate any foreign keys with a line and the correct "1" and "infinity" labels