Databases
StackOverflow2013
Postsdbo
POOne query per each entity
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOne query per each entity
    primarykey
    data
    text
    <p>Imagine we have an ArrayCollection, containing several Doctrine Entities instance of Country. Also imagine that my method 'getName()' is, in fact, a one to many relation with several languages ( A2lixTranslation support )...</p> <p>The point is that this ArrayCollection is built from ElasticSearch service, so when I retrieve all these entities, iterate them and print their name, is just an extra query for every category.</p> <p>I don't really know how to manage this situation, so 150 extra queries is not mainainable...</p> <h2>Example Implementation</h2> <pre><code>$countries = // ArrayCollection of Countries, returned by any mapping system. foreach ($countries as $country) { /** * As name is an entity, uses lazy loading in every iteration * Because I get collection as it comes, I would like to retrieve * all names in one query. I thought about perform a DQL with a join * of all countries and their names, so Doctrine will catch'em all * but only catch my query and results, and do not identify retrieved * results with my collection, so is not working... */ $name = $country-&gt;getName(); echo $name; } // Could be nice do something like this... $countries = // ArrayCollection of Countries, returned by any mapping system. $queryBuilder = $this -&gt;getDoctrine() -&gt;getRepository('ProjectCoreBundle:Country') -&gt;createQueryBuilder('c'); /** * This query result should only add Cache with results */ $queryBuilder -&gt;select('c','t') -&gt;innerJoin('c.countryName','cn','WITH','c.id = cn.Country') -&gt;getQuery() -&gt;getResult(); foreach ($countries as $country) { /** * At this poing, as Name relation entity is already loaded and cached * lazy load will simply return object ( Any query is performed ) */ $name = $country-&gt;getName(); echo $name; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USj0k
    1. USmmoreram
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CODo you have some code or pseudo-code of what your are trying to accomplish ? It would help to understand your problem.
      singulars
      1. POOne query per each entity
      1. USjackdbernier
    2. COYou want to replace your original query with one that joins the name relation. That way you will get everything you need on one gulp. Of course you might be surprised at how efficient these little lazy loading queries can be. After you get it working try running some bench marks. Could be that those extra queries won't have much impact at all due to caching.
      singulars
      1. POOne query per each entity
      1. USCerad
    3. CO@cerad Thanks. The point is that elasticSearch is actually doing this query, so at the moment is intouchable. And 600 query calls are too much...
      singulars
      1. POOne query per each entity
      1. USmmoreram
 

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