-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #835 from schmittjoh/ValueObjects
Value objects (Based on #634)
- Loading branch information
Showing
25 changed files
with
759 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
Separating Concerns using Embeddables | ||
------------------------------------- | ||
|
||
Embeddables are classes which are not entities themself, but are embedded | ||
in entities and can also be queried in DQL. You'll mostly want to use them | ||
to reduce duplication or separating concerns. | ||
|
||
For the purposes of this tutorial, we will assume that you have a ``User`` | ||
class in your application and you would like to store an address in | ||
the ``User`` class. We will model the ``Address`` class as an embeddable | ||
instead of simply adding the respective columns to the ``User`` class. | ||
|
||
.. configuration-block:: | ||
|
||
.. code-block:: php | ||
<?php | ||
/** @Entity */ | ||
class User | ||
{ | ||
/** @Embedded(class = "Address") */ | ||
private $address; | ||
} | ||
/** @Embeddable */ | ||
class Address | ||
{ | ||
/** @Column(type = "string") */ | ||
private $street; | ||
/** @Column(type = "string") */ | ||
private $postalCode; | ||
/** @Column(type = "string") */ | ||
private $city; | ||
/** @Column(type = "string") */ | ||
private $country; | ||
} | ||
.. code-block:: xml | ||
<doctrine-mapping> | ||
<entity name="User"> | ||
<embedded name="address" class="Address" /> | ||
</entity> | ||
<embeddable name="Address"> | ||
<field name="street" type="string" /> | ||
<field name="postalCode" type="string" /> | ||
<field name="city" type="string" /> | ||
<field name="country" type="string" /> | ||
</embeddable> | ||
</doctrine-mapping> | ||
.. code-block:: yaml | ||
User: | ||
type: entity | ||
embedded: | ||
address: | ||
class: Address | ||
Address: | ||
type: embeddable | ||
fields: | ||
street: { type: string } | ||
postalCode: { type: string } | ||
city: { type: string } | ||
country: { type: string } | ||
In terms of your database schema, Doctrine will automatically inline all | ||
columns from the ``Address`` class into the table of the ``User`` class, | ||
just as if you had declared them directly there. | ||
|
||
You can also use mapped fields of embedded classes in DQL queries, just | ||
as if they were declared in the ``User`` class: | ||
|
||
.. code-block:: sql | ||
SELECT u FROM User u WHERE u.address.city = :myCity | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.