Okay, I have looked into the code which is responsible for the object hydration and came to the conclusion, that my previous idea does not work, because during hydration I have no information about the query and its conditions. Plus Doctrine would have to manage two instances for the same database record, which could lead to inconsistence.
The next idea I had, was to extend the PersistentCollection with a filtered "view" which could be accessed from the parent entity. But this seems to be tricky, too. I am not sure if this functionality is implementable with the current way of hydration :-( but I'll think about it. Am Dienstag, 5. August 2014 14:09:19 UTC+2 schrieb Marco Pivetta: > > > On 4 August 2014 21:30, naitsirch <[email protected] <javascript:>> > wrote: > >> I'll see if I could create a patch and add a Pull Request on GitHub. >> Thanks for your reply, Marco. >> > > That would be awesome, thank you! > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > -- 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.
