Doctrine Project

Doctrine Project http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us

5.2.7

850

21-02-2013

[DDC-2051] after filtering an association by using ->matching(Criteria) original association changes http://www.doctrine-project.org/jira/browse/DDC-2051 Doctrine 2 - ORM <p>after filtering an association with a criteria it changes so it's not a normal collection and you can't re-filter it.</p> <p>even after hydrating it you can't filter it.</p> DDC-2051

after filtering an association by using ->matching(Criteria) original association changes

Bug Major Resolved Invalid All Benjamin Eberlei Koby Soto Tue, 2 Oct 2012 10:19:04 +0000 Mon, 15 Oct 2012 16:10:57 +0000 Mon, 15 Oct 2012 16:10:57 +0000 2.3 2.4 0 2 <p>The filtering only works once and only if the database hasn't been queried! </p> <p>This is a major bug because i would like to filter big collections more than once per request.</p> <p>Can you add a code example? I don't understand what you mean.</p> <p>sure: here's just an example (written right now to demonstrate, not taken from real project, so no criticize pls):</p> <p>Let's say we have two functions:</p> <p>1. function getExpensiveBooks($limit)</p> { $books = $this->getBooks(); //proxy, haven't queried yet. $criteria = Criteria::create()->where(Criteria::expr()->gt('price', '10'))->setMaxResults($limit); return $books->matching($criteria); } <p>2. function getCheapBooks($limit)</p> { $books = $this->getBooks(); //proxy, haven't queried yet. $criteria = Criteria::create()->where(Criteria::expr()->lt('price', '4'))->setMaxResults($limit); return $books->matching($criteria); } <p>now, let's say that in the controller i've called:<br/> $expensiveBooks = $author->getExpensiveBooks(3); //will work fine, and the query will be according the criteria.<br/> //but going on and doing this:<br/> $cheapBooks = $author->getCheapBooks(3); //will not work: matching is undefined function.</p> <p>It appears that doing matching only works on the first time on a certain association. </p> <p>this was due to inconsistent association type in both owner and target (target had one-to-one while owner had one-to-many)</p> <p>sorry</p>