From cd7f91910b9d5fc4bf0d6ba8f84c2b84e0959408 Mon Sep 17 00:00:00 2001 From: Eugene Dounar Date: Wed, 4 Feb 2015 00:17:13 +0300 Subject: [PATCH] Docs: Embeddable supported mappings Mention that only basic mapping is supported by embeddables --- docs/en/tutorials/embeddables.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/en/tutorials/embeddables.rst b/docs/en/tutorials/embeddables.rst index be565bf2c..8dc98b99e 100644 --- a/docs/en/tutorials/embeddables.rst +++ b/docs/en/tutorials/embeddables.rst @@ -3,7 +3,9 @@ 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. +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 +contain properties with basic ``@Column`` mapping. 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