Joins

Documentation status: reference — see Maturity and evidence.

A join combines several conceptual structures around explicit roles or relations.

The join should express a conjunction of meaning, not copy a SQL join into the model. Persistence can then optimize the composition.

Recommendations

• start from conceptual relations;
• name roles explicitly;
• project only the information that is needed;
• avoid table or column dependencies when the model already carries the meaning.