RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2024-12-13 14:56:01 +03:00
Code Issues Projects Releases Wiki Activity

[2.0] Fixed test case. All in-memory changes should be flushed before querying. That's how it works in other ORM tools too

Browse Source
This commit is contained in:
guilhermeblanco 2009-09-06 14:27:38 +00:00
parent 05568fa259
commit e0012f0750
1 changed files with 2 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
tests/Doctrine/Tests/ORM/Functional/StandardEntityPersisterTest.php
View File

@ -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();