This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
📖 Task Introduction
In relational databases, a many-to-many join across tables requires an intermediate join table. A similar concept exists in the Ontology, and in this exercise, you'll configure a many-to-many join between your passenger and flight alert object types.
🔨 Task Instructions
From the object type Overview page, scroll down to the Link Types block and click ⊕ Create new link type.
In the Choose an object type dropdown, select the [yourName] Flight Alert object type you created in Exercise 2.
Select Many as the cardinality for your Flight Alert object type and then agree to Change cardinality when prompted.
OMA will then ask you to define the join table that will enable the many-to-many relationship between your passengers and your flight alerts.
Select the passenger_flight_alerts dataset in your Ontology Project: Flight Alerts folder.
In the column dropdown for each object type, choose the respective primary keys: passenger_id for the Passenger object type and alert_display_name for Flight Alert.