RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-02 13:31:45 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #6766 from ThomasLandauer/patch-1

Browse Source 
Moved explanation out of PHP-Codeblock...
This commit is contained in:
Luís Cobucci 2017-10-26 09:49:48 +02:00 committed by GitHub
commit 0497f50ba6
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/en/reference/association-mapping.rst
View File

@ -33,7 +33,7 @@ inverse sides of associations <unitofwork-associations>`
Many-To-One, Unidirectional
---------------------------
A many-to-one association is the most common association between objects.
A many-to-one association is the most common association between objects. Example: Many Users have One Address:
.. configuration-block::
@ -46,7 +46,6 @@ A many-to-one association is the most common association between objects.
// ...
/**
* Many Users have One Address.
* @ManyToOne(targetEntity="Address")
* @JoinColumn(name="address_id", referencedColumnName="id")
*/
@ -796,7 +795,7 @@ Take an example of two entities ``Article`` and ``Tag``. Whenever
you want to connect an Article to a Tag and vice-versa, it is
mostly the Article that is responsible for this relation. Whenever
you add a new article, you want to connect it with existing or new
tags. Your create Article form will probably support this notion
tags. Your "Create Article" form will probably support this notion
and allow specifying the tags directly. This is why you should pick
the Article as owning side, as it makes the code more
understandable: