Doctrine Entity Mapping

When to use

• The user must pick a primary key and an id generation strategy (auto, identity, sequence, or UUID) for a Doctrine entity.
• The user needs to map PHP property types to Doctrine column types, lengths, and nullability.
• The user needs to declare how a PHP class maps to a table with Doctrine — entity, columns, and identifier.

When NOT to use

• Do not use Doctrine mapping attributes on an Active Record model (for example an Eloquent model) that already maps itself by convention.
• Do not map an entity for data that is only queried read-only and never persisted, such as ad-hoc report rows.

Core guidance