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

Koby Soto added a comment - 15/Oct/12 4:10 PM this was due to inconsistent association type in both owner and target (target had one-to-one while owner had one-to-many) sorry

Koby Soto added a comment - 07/Oct/12 8:34 AM sure: here's just an example (written right now to demonstrate, not taken from real project, so no criticize pls): Let's say we have two functions: 1. function getExpensiveBooks($limit) { $books = $this->getBooks(); //proxy, haven't queried yet. $criteria = Criteria::create()->where(Criteria::expr()->gt('price', '10'))->setMaxResults($limit); return $books->matching($criteria); } 2. function getCheapBooks($limit) { $books = $this->getBooks(); //proxy, haven't queried yet. $criteria = Criteria::create()->where(Criteria::expr()->lt('price', '4'))->setMaxResults($limit); return $books->matching($criteria); } now, let's say that in the controller i've called: $expensiveBooks = $author->getExpensiveBooks(3); //will work fine, and the query will be according the criteria. //but going on and doing this: $cheapBooks = $author->getCheapBooks(3); //will not work: matching is undefined function. It appears that doing matching only works on the first time on a certain association.

Benjamin Eberlei added a comment - 06/Oct/12 9:30 AM Can you add a code example? I don't understand what you mean.

Koby Soto added a comment - 02/Oct/12 10:27 AM The filtering only works once and only if the database hasn't been queried! This is a major bug because i would like to filter big collections more than once per request.