Challenge: Create and Use New Model Associations

Next ❯ ❯❯

Task

Create an “arrival” association between the Airport and Flight classes.
Seed the database with “arrival” association links between Airport and Flight objects.
Instantiate and save a new Flight object, using getter and setter methods to manage it association links.
Delete an Airport object along with its associated Flight objects.

Reset and reseed the database:

Create “arrival” association:

Create an “arrival” association between the Airport and Flight classes as per the class diagram below (see label Ⓐ).
📸 Screenshot model-2-01: The VS Code editor showing the new migration file that adds the foreign key column for the association.
📸 Screenshot model-2-02: The VS Code editor showing the Airport class definition with the new has_many declaration visible.
📸 Screenshot model-2-03: The VS Code editor showing the Flight class definition with the new belongs_to declaration visible.

Seed database with association links:

Use the seeds.rb script to seed the database with new association links as per the object diagram below (see labels Ⓐ Ⓑ Ⓒ).
💡 Hint: The database must be reset before running the updated seeds script lest erroneous duplicate seed data be saved in the database.
📸 Screenshot model-2-04: The VS Code editor showing the seeds.rb file with code creating the new association links visible.
📸 Screenshot model-2-05: The Rails console showing the result of Flight.all with foreign key values for the new links visible.

Create a new Flight and link it to departure and arrival airports:

In the Rails console, retrieve the following Airport objects:
- LAX, storing a reference to it in variable lax.
- ATL, storing a reference to it in variable atl.
Instantiate a new Flight object (unsaved), which will represent a flight from LAX to ATL, as follows:
- Departure Time: 07-21-2028 11:05:00 AM
- Arrival Time: 07-21-2028 01:35:00 PM
- Store result in variable lax_atl.
Using the lax_atl variable, set the flight’s association links as follows:
- departure_airport references the LAX Airport object.
- arrival_airport references the ATL Airport object.
Using the lax_atl variable, save the new Flight object and its association links to the database.
💡 Hint: Successful completion of this step will produce the configuration depicted in the object diagram below.
📸 Screenshot model-2-06: The Rails console showing the results of lax_atl.departure_airport and lax_atl.arrival_airport with the resultant Airport object output visible.

Delete a parent Airport object along with all its child Flight objects:

Retrieve the MEM Airport object, storing a reference to it in variable mem.
Using the mem variable, destroy the MEM Airport object.
- The Flight objects with MEM as their departure or arrival airports should be automatically deleted (as per the dependent: :destroy argument in the Airport class’ has_many declarations).
📸 Screenshot model-2-07: The Rails console showing the results of Airport.all and Flight.all with it being from the output that the MEM airport and its associated flights were deleted.

Submit Word DOCX file containing your screenshots to the designated Canvas assignment.