Question 2 Please

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. 2. Creating a Relational Database Schema Draw a relational database schema to track the organizational structure, finances, and events for a student club. For example, you might consider tracking current and past members of the club, along with information about that member, when they joined, and whether they are currently active; official positions within the club and who has held those positions and when; events organized by the club, along with who organized the event, who attended the event, and what items were purchased as part of that event; elections for officers of the club; and information about prospective members including a member contact person. The schema must consist of at least four tables with a total of at least 20 fields (eg. five fields each), and there must be at least three one-to-many relationships illustrated. Label the "1" and the "many" ends of each relationship. The 1 typically belongs to the end that is a key for the corresponding table. Also, underline the primary key of each table. Then, create tables in SQLite Studio that correspond to your schema, making sure to create foreign keys and primary keys that correspond to your schema. Populate each table with at least 4 rows. Include: Your schema (you can draw this on paper and take a photo) - A screenshot of the Structure page from SQLite Studio for each of your tables - A screenshot of the Data" page for each of your tables - A screenshot of the "Constraints" page for each of your tables To help the TAs understand the foreign key relationships in your schema, please include a 1-line description of each foreign key relationship. This is optional, but will help the TAS understand whether your foreign key relationships make sense. 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. 2. Creating a Relational Database Schema Draw a relational database schema to track the organizational structure, finances, and events for a student club. For example, you might consider tracking current and past members of the club, along with information about that member, when they joined, and whether they are currently active; official positions within the club and who has held those positions and when; events organized by the club, along with who organized the event, who attended the event, and what items were purchased as part of that event; elections for officers of the club; and information about prospective members including a member contact person. The schema must consist of at least four tables with a total of at least 20 fields (eg. five fields each), and there must be at least three one-to-many relationships illustrated. Label the "1" and the "many" ends of each relationship. The 1 typically belongs to the end that is a key for the corresponding table. Also, underline the primary key of each table. Then, create tables in SQLite Studio that correspond to your schema, making sure to create foreign keys and primary keys that correspond to your schema. Populate each table with at least 4 rows. Include: Your schema (you can draw this on paper and take a photo) - A screenshot of the Structure page from SQLite Studio for each of your tables - A screenshot of the Data" page for each of your tables - A screenshot of the "Constraints" page for each of your tables To help the TAs understand the foreign key relationships in your schema, please include a 1-line description of each foreign key relationship. This is optional, but will help the TAS understand whether your foreign key relationships make sense