Databases
StackOverflow2013
Postsdbo
POHow to optimize MySQL Views
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to optimize MySQL Views
    primarykey
    data
    text
    <p>I have some querys using views, and these run a lot slower than I would expect them to given all relevant tables are indexed (and not that large anyway).</p> <p>I hope I can explain this:</p> <p>My main Query looks like this (grossly simplified)</p> <pre><code>select [stuff] from orders as ord left join calc_order_status as ors on (ors.order_id = ord.id) </code></pre> <p><code>calc_order_status</code> is a view, defined thusly:</p> <pre><code>create view calc_order_status as select ord.id AS order_id, (sum(itm.items * itm.item_price) + ord.delivery_cost) AS total_total from orders ord left join order_items itm on itm.order_id = ord.id group by ord.id </code></pre> <p>Orders (ord) contain orders, <code>order_items</code> contain the individual items associated with each order and their prices.</p> <p>All tables are properly indexed, BUT the thing runs slowly and when I do a EXPLAIN I get</p> <pre><code> # id select_type table type possible_keys key key_len ref rows Extra 1 1 PRIMARY ord ALL customer_id NULL NULL NULL 1002 Using temporary; Using filesort 2 1 PRIMARY &lt;derived2&gt; ALL NULL NULL NULL NULL 1002 3 1 PRIMARY cus eq_ref PRIMARY PRIMARY 4 db135147_2.ord.customer_id 1 Using where 4 2 DERIVED ord ALL NULL NULL NULL NULL 1002 Using temporary; Using filesort 5 2 DERIVED itm ref order_id order_id 4 db135147_2.ord.id 2 </code></pre> <p>My guess is, "derived2" refers to the view. The individual items (itm) seem to work fine, indexed by order _ id. The problem seems to be Line # 4, which indicates that the system doesn't use a key for the orders table (ord). But in the MAIN query, the order id is already defined: left join calc_order_status as ors on (ors.order _ id = ord.id) and ord.id (both in the main query and within the view) refer to the primary key.</p> <p>I have read somewhere than MySQL simpliy does not optimize views that well and might not utilize keys under some conditions even when available. This seems to be one of those cases. </p> <p>I would appreciate any suggestions. Is there a way to force MySQL to realize "it's all simpler than you think, just use the primary key and you'll be fine"? Or are views the wrong way to go about this at all?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjms
    1. USjms
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to optimize MySQL Views
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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