Please answer correctly and straightforwardly, and I will give you a thumbs up. please do not copy the old answers. thank you
AIRPORT \begin{tabular}{|l|l|l|l|} \hline Airport_code & Name & City & State \\ \hline \end{tabular} FLIGHT \begin{tabular}{|l|l|l|} \hline Flight_number & Airline & Weekdays \\ \hline \end{tabular} FLIGHT_LEG \begin{tabular}{|l|c|c|c} \hline Flight_number & Leg_number & Departure_airport_code & Scheduled_departure_time \\ \hline & Arrival_airport_code & Scheduled_arrival_time \\ \hline \end{tabular} LEG_INSTANCE \begin{tabular}{|c|c|c|c|c|c|c|} \hline Flight_number & Leg_number & Date & Number_of_available_seats & Airplane_id \\ \hline \hline Departure_airport_code & Departure_time & Arrival_airport_code & Arrival_time \\ \hline \end{tabular} FARE \begin{tabular}{|l|l|l|l|} \hline Flight_number & Fare_code & Amount & Restrictions \\ \hline \end{tabular} AIRPLANE_TYPE \begin{tabular}{|l|l|l|} \hline Airplane_type_name & Max_seats & Company \\ \hline \end{tabular} CAN_LAND \begin{tabular}{|l|l|} \hline Airplane_type_name & Airport_code \\ \hline \end{tabular} AIRPLANE \begin{tabular}{|l|l|l|} \hline Airplane_id & Total_number_of_seats & Airplane_type \\ \hline \end{tabular} SEAT_RESERVATION \begin{tabular}{|l|l|l|l|l|l|} \hline Flight_number & Leg_number & Date & Seat_number & Customer_name & Customer_phone \\ \hline \end{tabular} Consider the AIRLINE relational database schema and some sample data given in APPENDIX A. The schema describes a database for airline flight information. Each flight is identified by a Flight_number, and consists of one or more FLIGHT_LEGs with Leg_numbers 1, 2, 3, ... Each FLIGHT_LEG has scheduled arrival and departure times, airports, and one or more LEG_INSTANCEs one for each Date on which the flight travels. FAREs are kept for each FLIGHT. For each FLIGHT_LEG instance, SEAT_RESERVATIONs are kept, as are the AIRPLANE used on the leg and the actual arrival and departure times and airports. An AIRPLANE is identified by an Airplane_id and is of a particular AIRPLANE_TYPE. CAN_LAND relates AIRPLANE_TYPEs to the AIRPORTs at which they can land. An AIRPORT is identified by an Airport_code. a) Develop the database schema diagram that shows the tables, columns, primary keys and the referential integrity constraints (foreign keys) that must hold on the AIRPORT database. Your diagram must be a neat readable diagram (preferably not hand-drawn, or use straight readable line if drawn by hand). Use Hay's principle of schema layout. b) If the AIRLINE database needs to enter a new reservation (of your choice) for some trip on a specific date, describe the operations that would need to be performed for the reservation to be created. Assume that any required information in other relations has been entered, flights cannot be overbooked, and the new reservation has 2 leg instances. You may make up the data to show the operations that need to be performed to create the reservation. The operations do not need to be expressed in SQL. c) For each of the operations identified above, identify if the constraints that will be checked during the operation are key, entity integrity, referential integrity, or general constraints specific to the AIRLINE database. d) Thinking about the operation of the AIRLINE database, describe one other example of a general constraint (i.e., neither implicit nor schema based) that could be imposed on the database. You are not required to provide the SQL statement to implement this constraint in the database
