If you have a bunch of records, @cascade is going to read all of them anyway, and then filter those out. It would be quicker to stick with DQL. I would suggest you do a custom dql query for your use case.
J
If you have a bunch of records, @cascade is going to read all of them anyway, and then filter those out. It would be quicker to stick with DQL. I would suggest you do a custom dql query for your use case.
J