Databases
StackOverflow2013
Postsdbo
POMySQL Query performance help, many of the same table being joined
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMySQL Query performance help, many of the same table being joined
    primarykey
    data
    text
    <p>I am writing a PHP script that creates an SQL query. This script and database is for the Joomla CMS, and specifically it's querying the SOBIPro component's tables (to use the data entered there in this component). However, due to the way that the SOBI Pro tables are handled, with each instance of a field being its own row in a table, this means including a separate instance of the table for every field I want to pull back. This doesn't seem very efficient, and in fact in this one search it times out.</p> <p>The SQL query is as follows (this is after being generated by my PHP code):</p> <pre><code> SELECT DISTINCT o.id AS entryid, o.parent AS parentID, name.baseData AS title,business.baseData AS business_data, contact_fn.baseData AS contact_fn_data ,contact_ln.baseData AS contact_ln_data ,position.baseData AS position_data, civic1.baseData AS civic1_data ,civic2.baseData AS civic2_data ,mailing.baseData AS mailing_data, community.baseData AS community_data ,municip.baseData AS municip_data ,county.baseData AS county_data, province.baseData AS province_data ,country.baseData AS country_data ,postal.baseData AS descr_data, phone.baseData AS phone_data ,tollfree.baseData AS tollfree_data ,fax.baseData AS fax_data, email.baseData AS email_data ,web.baseData AS web_data ,empTotal.baseData AS empTotal_data FROM jos_sobipro_object AS o INNER JOIN jos_sobipro_field_data AS name ON name.sid = o.id INNER JOIN jos_sobipro_relations AS r ON o.id = r.id LEFT JOIN jos_sobipro_field_data AS business ON business.sid = o.id AND business.fid = 36 LEFT JOIN jos_sobipro_field_data AS contact_fn ON contact_fn.sid = o.id AND contact_fn.fid = 74 LEFT JOIN jos_sobipro_field_data AS contact_ln ON contact_ln.sid = o.id AND contact_ln.fid = 75 LEFT JOIN jos_sobipro_field_data AS position ON position.sid = o.id AND position.fid = 76 LEFT JOIN jos_sobipro_field_data AS civic1 ON civic1.sid = o.id AND civic1.fid = 77 LEFT JOIN jos_sobipro_field_data AS civic2 ON civic2.sid = o.id AND civic2.fid = 78 LEFT JOIN jos_sobipro_field_data AS mailing ON mailing.sid = o.id AND mailing.fid = 79 LEFT JOIN jos_sobipro_field_data AS community ON community.sid = o.id AND community.fid = 80 LEFT JOIN jos_sobipro_field_data AS municip ON municip.sid = o.id AND municip.fid = 81 LEFT JOIN jos_sobipro_field_data AS county ON county.sid = o.id AND county.fid = 82 LEFT JOIN jos_sobipro_field_data AS province ON province.sid = o.id AND province.fid = 83 LEFT JOIN jos_sobipro_field_data AS country ON country.sid = o.id AND country.fid = 84 LEFT JOIN jos_sobipro_field_data AS postal ON postal.sid = o.id AND postal.fid = 85 LEFT JOIN jos_sobipro_field_data AS phone ON phone.sid = o.id AND phone.fid = 86 LEFT JOIN jos_sobipro_field_data AS tollfree ON tollfree.sid = o.id AND tollfree.fid = 87 LEFT JOIN jos_sobipro_field_data AS fax ON fax.sid = o.id AND fax.fid = 88 LEFT JOIN jos_sobipro_field_data AS email ON email.sid = o.id AND email.fid = 89 LEFT JOIN jos_sobipro_field_data AS web ON web.sid = o.id AND web.fid = 90 LEFT JOIN jos_sobipro_field_data AS empTotal ON empTotal.sid = o.id AND empTotal.fid = 106 WHERE o.approved = 1 AND o.oType = 'entry' AND name.fid = 36 AND name.baseData &lt;&gt; '' AND name.section = 54 AND r.pid IN (415,418,425,431,458) AND (municip.baseData = "Municipality Name") ORDER BY name.baseData ASC </code></pre> <p>It seems to work decently fast as long as the municip.baseData search isn't involved, in which case it flops even at 15 entries in the directory. There has to be a better way to get this SQL code designed, while still bringing back all of the fields needed. This query is called via AJAX, and eventually there will be 2000+ entries in the directory.</p> <p>EDIT: Here is the EXPLAIN output, as requested:</p> <pre><code> id select_type table type possible_keys key key_len ref rows Extra 1 SIMPLE name ref PRIMARY PRIMARY 8 const,const 15 Using where; Using temporary; Using filesort 1 SIMPLE municip ref PRIMARY PRIMARY 4 const 9 Using where 1 SIMPLE o eq_ref PRIMARY,oType PRIMARY 4 [[dbname]].municip.sid 1 Using where 1 SIMPLE county ref PRIMARY PRIMARY 4 const 10 1 SIMPLE province ref PRIMARY PRIMARY 4 const 10 1 SIMPLE country ref PRIMARY PRIMARY 4 const 8 1 SIMPLE postal ref PRIMARY PRIMARY 4 const 9 1 SIMPLE business ref PRIMARY PRIMARY 4 const 15 1 SIMPLE contact_fn ref PRIMARY PRIMARY 4 const 9 1 SIMPLE contact_ln ref PRIMARY PRIMARY 4 const 9 1 SIMPLE position ref PRIMARY PRIMARY 4 const 9 1 SIMPLE civic1 ref PRIMARY PRIMARY 4 const 10 1 SIMPLE civic2 ref PRIMARY PRIMARY 4 const 9 1 SIMPLE phone ref PRIMARY PRIMARY 4 const 10 1 SIMPLE tollfree ref PRIMARY PRIMARY 4 const 9 1 SIMPLE fax ref PRIMARY PRIMARY 4 const 10 1 SIMPLE email ref PRIMARY PRIMARY 4 const 9 1 SIMPLE mailing ref PRIMARY PRIMARY 4 const 11 1 SIMPLE community ref PRIMARY PRIMARY 4 const 9 1 SIMPLE web ref PRIMARY PRIMARY 4 const 10 1 SIMPLE empTotal ref PRIMARY PRIMARY 4 const 10 1 SIMPLE r ref PRIMARY PRIMARY 4 [[dbname]].name.sid 3 Using where; Using index; Distinct </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USwolfergiga
    1. USwolfergiga
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMySQL Query performance help, many of the same table being joined
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMySQL Query performance help, many of the same table being joined
      1. This table or related slice is empty.
      1. VTUpMod
    1. CORun a sql EXPLAIN on this query, post the output.
      singulars
      1. POMySQL Query performance help, many of the same table being joined
      1. USBen Lee
    2. COhttp://dev.mysql.com/doc/refman/5.1/en/using-explain.html
      singulars
      1. POMySQL Query performance help, many of the same table being joined
      1. USBen Lee
    3. COEXPLAIN output added to the main text.
      singulars
      1. POMySQL Query performance help, many of the same table being joined
      1. USwolfergiga
 

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