Doctrine Associations

When to use

• The user sees many repeated queries when iterating a Doctrine collection and needs to fix the N+1 problem.
• The user must decide which side of a bidirectional Doctrine association owns the relationship and holds the foreign key.
• The user needs to model a relationship between Doctrine entities — one-to-many, many-to-one, or many-to-many.

When NOT to use

• Do not create a direct ORM association across a bounded-context or aggregate boundary that should be referenced by id only.
• Do not map an association when one entity only needs another's identifier value, not a navigable object graph.

Core guidance