if you access the collection in a request that doesnt construct the entity
from database, then yes. examples:

1. request that creates the entity (instead of updating)
2. tests

On Thu, Oct 22, 2015 at 10:59 PM, matthew_be <[email protected]> wrote:

> Hi,
>
> I wonder if I really need to  initialize my collections with *new
> ArrayCollection()* in the constructor (as suggested in the docs), as
> Dotrine seems to replace these by a *PersistentCollection* instance.
>
> Thank you for any clarification,
> Matthew
>
> --
> You received this message because you are subscribed to the Google Groups
> "doctrine-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/doctrine-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to