From 19dcd629c0bb0d4f838fc331709a55e6437e21d5 Mon Sep 17 00:00:00 2001 From: Maciej Malarz Date: Tue, 3 Oct 2017 17:14:06 +0200 Subject: [PATCH] [DOCS] Emphasize that Embeddable can only contains simple fields --- docs/en/tutorials/embeddables.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/en/tutorials/embeddables.rst b/docs/en/tutorials/embeddables.rst index 1dcb3c147..483e58d9d 100644 --- a/docs/en/tutorials/embeddables.rst +++ b/docs/en/tutorials/embeddables.rst @@ -4,8 +4,11 @@ Separating Concerns using Embeddables 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 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. +or address are the primary use case for this feature. + +.. note:: + + 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