RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2024-12-14 23:26:04 +03:00
Code Issues Projects Releases Wiki Activity

Fix code box in Note

Browse Source
This commit is contained in:
Benjamin Eberlei 2010-07-23 23:43:44 +02:00
parent e0c702d068
commit 3b76ea9ffe
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
manual/en/working-with-objects.txt
View File

@ -448,14 +448,14 @@ and encapsulating all the details inside the classes can be challenging.
> >
> If you want to make sure that your collections are perfectly encapsulated you should not return > If you want to make sure that your collections are perfectly encapsulated you should not return
> them from a `getCollectionName()` method directly, but call `$collection->toArray()`. This way a client programmer > them from a `getCollectionName()` method directly, but call `$collection->toArray()`. This way a client programmer
> for the entity cannot circumvent the logic you implement on your entity for association management. Example: > for the entity cannot circumvent the logic you implement on your entity for association management. For example:
>
> [php] [php]
> class User { class User {
> public function getReadComments() { public function getReadComments() {
> return $this->commentsRead->toArray(); return $this->commentsRead->toArray();
> } }
> } }
There is no single, best way for association management. It greatly depends on the requirements of your concrete There is no single, best way for association management. It greatly depends on the requirements of your concrete
domain model as well as your preferences. domain model as well as your preferences.