Skip to content

Explain another option to override bundle's entity mapping #10053

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 25, 2018
Merged

Explain another option to override bundle's entity mapping #10053

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions bundles/override.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,11 +71,14 @@ For more information on compiler passes, see :doc:`/service_container/compiler_p
Entities & Entity Mapping
-------------------------

Due to the way Doctrine works, it is not possible to override entity mapping
of a bundle. However, if a bundle provides a mapped superclass (such as the
``User`` entity in the FOSUserBundle) one can override attributes and
associations. Learn more about this feature and its limitations in
`the Doctrine documentation`_.
If a bundle defines its entity mapping in configuration files instead of
annotations, you can override them as any other regular bundle configuration
file. The only caveat is that you must override all those mapping configuration
files and not just the ones you actually want to override.

If a bundle provides a mapped superclass (such as the ``User`` entity in the
FOSUserBundle) you can override its attributes and associations. Learn more
about this feature and its limitations in `the Doctrine documentation`_.

Forms
-----
Expand Down