Batch processing with doctrine is trickier than it seems, even with the help of iterate() and IterableResult. Just as you expected greatest benefit of IterableResult is that it does not load all of the elements into memory, and the second benefit is that it doesn’t hold references to the entities you load, thus IterableResult doesn’t … Read more
Paginate was merged with doctrine 2.2 And the new symfony2 release 2.0.10 is compatible with. Now use it like that //use Doctrine paginator use Doctrine\ORM\Tools\Pagination\Paginator; Write your query then call results like that. $query->setMaxResults($limit); $query->setFirstResult($offset); $results = new Paginator($query, $fetchJoin = true); Hope this will help you. Note: If you are using SF2 2.0.10, you … Read more
The getResult() always returns an array. If you want a collection, you must pass the array that is returned by getResult() to Doctrine’s ArrayCollection e.g. use Doctrine\Common\Collections\ArrayCollection; $result = $this ->getEntityManager() ->createQueryBuilder() ->select(‘p’) ->from(‘…\Player’, ‘p’) ->getQuery() ->getResult() ; $players = new ArrayCollection($result);
You can catch the UniqueConstraintViolationException as such: use Doctrine\DBAL\Exception\UniqueConstraintViolationException; // … try { // … $em->flush(); } catch (UniqueConstraintViolationException $e) { // …. }
According to your code, you already have an EntityManager injected. You don’t need to call $em = $this->get(‘doctrine’)->getEntityManager() — just use $this->em. If you don’t inject an EntityManager already, read this. UPDATE: You need to make the container inject an EntityManager into your service. Here’s an example of doing it in config.yml: services: your.service: class: … Read more
You should add the option onDelete=”SET NULL” in the annotation of your entity Publication like this: class Publication { /** * @ORM\ManyToOne(targetEntity=”Teacher”, inversedBy=”publications”) * @ORM\JoinColumn(name=”teacher_id”, referencedColumnName=”id”, onDelete=”SET NULL”) */ protected $teacher; } This modification is registered in the table declaration itself. Hence, you need a database migration or a schema change for this to take … Read more
Although your solution work fine with MySQL, I failed to make it work with PostgreSQL as It’s sequence based. I’ve to add this line to make it work perfectly : $metadata->setIdGenerator(new \Doctrine\ORM\Id\AssignedGenerator());