Correct: class metadata only allows you to define how an association will be handled in your DB at FK level, as well as how it will be loaded and saved by the ORM by honoring that FK's constraints.
The approaches that can be taken are: - filtering in your getter, by using the `Selectable` API fo the collection - filtering via an SQL filter (only do this if you know what you are doing Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 16 March 2014 00:18, Stan Lemon <[email protected]> wrote: > If I understand what you're saying, the filtering can't be done on the > class metadata for an association, is that correct? > > -- > 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.
