title: Multiple query vs Single (multiple has many joins)
body: <p>Recently stumbled on this situation. Doing both queries might be "light" in my situation, I just want to know when it comes to big dataset on what is better. Better in overall (performance, speed, etc etc).</p>
  
  <p>Currently I do single queries of 2 1:N (has-many) relationship and reduce/transform the data in the application.</p>
  
  <p>It looks like this transformed/reduced:</p>
  
  <pre><code>[
    'field' =&gt; 'value',
    'hasMany-1' =&gt; [],
    'hasMany-2' =&gt; []
  ]
  </code></pre>
  
  <p>I'm actually somehow tempted to just do separate queries as it eliminates the pain of reducing it if I had more than 2 hasMany queries and is more quite readable but code currently works so I'll maybe just do it next time.</p>
  
  <p>Is the compromise worth it? Again, in my situation it might be very "light" as I only have few rows (&lt; 100) and structure is not complex as it is on early stage yet.</p>
  
  <p>But asked in case I stumble upon this next time and when dataset grows larger.</p>
  
  <p>** EDIT **</p>
  
  <p>So the has-many relationship I'm talking about are: A <code>customer</code> has-many <code>phones</code> and <code>pets</code>.</p>
  
  <p>My current query returns me this result (simplified):</p>
  
  <pre><code>customer_id | pet_name | phone
  1           | john     | 1234
  1           | john     | 5678
  2           | jane     | 1357
  2           | jane     | 2468
  2           | joe      | 1357
  2           | joe      | 2468
  </code></pre>
  
  <p>I think my query is fine. It seems logical for some rows to repeat because the other field has different value.</p>