Skip to content

Updated cookbook title to match the usual format and added index entries #1724

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
Sep 18, 2012
Merged

Updated cookbook title to match the usual format and added index entries #1724

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
10 changes: 7 additions & 3 deletions cookbook/doctrine/resolve_target_entity.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
Defining Relationships with Abstract Classes and Interfaces
===========================================================
.. index::
single: Doctrine; Resolving target entities
single: Doctrine; Define relationships with abstract classes and interfaces

How to Define Relationships with Abstract Classes and Interfaces
================================================================

.. versionadded: 2.1
The ResolveTargetEntityListener is new to Doctrine 2.2, which was first
Expand Down Expand Up @@ -155,4 +159,4 @@ Final Thoughts
With the ``ResolveTargetEntityListener``, you are able to decouple your
bundles, keeping them usable by themselves, but still being able to
define relationships between different objects. By using this method,
your bundles will end up being easier to maintain independently.
your bundles will end up being easier to maintain independently.