RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-09 00:39:25 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #6746 from doctrine/malarzm-patch-1

Browse Source 
[DOCS] Emphasize that Embeddable can only contain simple fields
This commit is contained in:
Marco Pivetta 2017-10-03 17:42:31 +02:00 committed by GitHub
commit 2ade863bca
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/en/tutorials/embeddables.rst
View File

@ -4,8 +4,11 @@ Separating Concerns using Embeddables
Embeddables are classes which are not entities themselves, but are embedded Embeddables are classes which are not entities themselves, but are embedded
in entities and can also be queried in DQL. You'll mostly want to use them in entities and can also be queried in DQL. You'll mostly want to use them
to reduce duplication or separating concerns. Value objects such as date range to reduce duplication or separating concerns. Value objects such as date range
or address are the primary use case for this feature. Embeddables can only or address are the primary use case for this feature.
contain properties with basic ``@Column`` mapping.
.. note::
Embeddables can only contain properties with basic ``@Column`` mapping.
For the purposes of this tutorial, we will assume that you have a ``User`` 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 class in your application and you would like to store an address in