Databases
StackOverflow2013
Postsdbo
POSymfony2 + Doctrine2 is not caching results of joined entities
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSymfony2 + Doctrine2 is not caching results of joined entities
    primarykey
    data
    text
    <p>I am using Symfony 2.0.10 with Doctrine 2.1 and have rather simple query (see below), where I want to cache results with APC (version 3.1.7, enabled 1GB of memory for it) via <code>useResultCache(true, 600)</code> and keep hydration mode as <code>\Doctrine\ORM\Query::HYDRATE_OBJECT</code>.</p> <p>The problem is that Many-to-Many relations (<code>Doctrine\ORM\PersistentCollection</code>) don't get cached and every time when main query results are cached the joined entities are set to <code>null</code>. The same query is cached well in APC when I set hydration mode to <code>\Doctrine\ORM\Query::HYDRATE_ARRAY</code>, but it is not acceptable solution for me, because I can't redo many templates for this to work.</p> <p>Please suggest how can I cache all joined entities' properties in APC? Please don't point to documentation, because I think I have learned it by heart trying to solve this issue :)</p> <h3>CODE:</h3> <pre><code>$property = $em -&gt;createQueryBuilder() -&gt;select('p,u') -&gt;from('MyBundle:Property', 'p') -&gt;leftJoin('p.users', 'u') -&gt;where('p.id in (:id)') -&gt;setParameter('id', 123) -&gt;getQuery() -&gt;useResultCache(true, 60) -&gt;setHydrationMode(\Doctrine\ORM\Query::HYDRATE_OBJECT) -&gt;getResult(); </code></pre> <h3>User.php</h3> <pre><code>class User { /** * @ORM\ManyToMany(targetEntity="Property", mappedBy="users", cascade={"all"}, fetch="EAGER") */ protected $properties; } </code></pre> <h3>Property.php</h3> <pre><code>class Property { /** * @ORM\ManyToMany(targetEntity="User", inversedBy="properties", cascade={"all"}, fetch="EAGER") * @ORM\JoinTable(name="user_property", * joinColumns={@ORM\JoinColumn(name="property_id", referencedColumnName="id")}, * inverseJoinColumns={@ORM\JoinColumn(name="user_id", referencedColumnName="id")} * ) */ protected $users; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAnton Babenko
    1. USAnton Babenko
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSymfony2 + Doctrine2 is not caching results of joined entities
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSymfony2 + Doctrine2 is not caching results of joined entities
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSymfony2 + Doctrine2 is not caching results of joined entities
      1. USMicE
      1. VTFavorite
    1. COdoes apc have enough free memory to cache your objects?
      singulars
      1. POSymfony2 + Doctrine2 is not caching results of joined entities
      1. USmeze
    2. CO@meze: Yes, enabled 1GB, which is more than enough for this case. APC version is 3.1.7, if matters.
      singulars
      1. POSymfony2 + Doctrine2 is not caching results of joined entities
      1. USAnton Babenko
    3. COCould you check if this works in 2.2? It has been released today and some fixes to caching mechanisms have been applied.
      singulars
      1. POSymfony2 + Doctrine2 is not caching results of joined entities
      1. USOcramius
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload