From e0012f075058c49a3dd3be061b228e6db7a04cf3 Mon Sep 17 00:00:00 2001
From: guilhermeblanco <guilhermeblanco@625475ce-881a-0410-a577-b389adb331d8>
Date: Sun, 6 Sep 2009 14:27:38 +0000
Subject: [PATCH] [2.0] Fixed test case. All in-memory changes should be
 flushed before querying. That's how it works in other ORM tools too

---
 .../Functional/StandardEntityPersisterTest.php    | 15 ++-------------
 1 file changed, 2 insertions(+), 13 deletions(-)

diff --git a/tests/Doctrine/Tests/ORM/Functional/StandardEntityPersisterTest.php b/tests/Doctrine/Tests/ORM/Functional/StandardEntityPersisterTest.php
index 2834173f8..d3979d4c3 100644
--- a/tests/Doctrine/Tests/ORM/Functional/StandardEntityPersisterTest.php
+++ b/tests/Doctrine/Tests/ORM/Functional/StandardEntityPersisterTest.php
@@ -84,23 +84,12 @@ class StandardEntityPersisterTest extends \Doctrine\Tests\OrmFunctionalTestCase
             }
         }
         
-        // Now we test how Hydrator affects IdentityMap
+        // Now we test how Hydrator affects IdentityMap 
+        // (change from ArrayCollection to PersistentCollection)
         $f3 = new ECommerceFeature();
         $f3->setDescription('XVID');
         $p->addfeature($f3);
         
-        $q = $this->_em->createQuery(
-            'SELECT p, f
-               FROM Doctrine\Tests\Models\ECommerce\ECommerceProduct p
-               JOIN p.features f'
-        );
-        
-        $res = $q->getResult();
-        
-        // $p is our in-memory object... it should still contain the
-        // not yet managed Feature (it can't get lost)
-        $this->assertEquals(3, count($p->getFeatures()));
-        
         // Now we persist the Feature #3
         $this->_em->persist($p);
         $this->_em->flush();