No cache version.

Caching disabled. Default setting for this page:enabled (code DEF204)
If the display is too slow, you can disable the user mode to view the cached version.

Rechercher dans le manuel MySQL

8.2.1.21 Row Constructor Expression Optimization

Contents

Row constructors permit simultaneous comparisons of multiple values. For example, these two statements are semantically equivalent:

  1. SELECT * FROM t1 WHERE (column1,column2) = (1,1);
  2. SELECT * FROM t1 WHERE column1 = 1 AND column2 = 1;

In addition, the optimizer handles both expressions the same way.

The optimizer is less likely to use available indexes if the row constructor columns do not cover the prefix of an index. Consider the following table, which has a primary key on (c1, c2, c3):

  1. CREATE TABLE t1 (
  2.   c1 INT, c2 INT, c3 INT, c4 CHAR(100),
  3.   PRIMARY KEY(c1,c2,c3)
  4. );

In this query, the WHERE clause uses all columns in the index. However, the row constructor itself does not cover an index prefix, with the result that the optimizer uses only c1 (key_len=4, the size of c1):

  1. mysql> EXPLAIN SELECT * FROM t1
  2.        WHERE c1=1 AND (c2,c3) > (1,1)\G
  3. *************************** 1. row ***************************
  4.            id: 1
  5.   select_type: SIMPLE
  6.         table: t1
  7.    partitions: NULL
  8.          type: ref
  9. possible_keys: PRIMARY
  10.           key: PRIMARY
  11.       key_len: 4
  12.           ref: const
  13.          rows: 3
  14.      filtered: 100.00
  15.         Extra: Using where

In such cases, rewriting the row constructor expression using an equivalent nonconstructor expression may result in more complete index use. For the given query, the row constructor and equivalent nonconstructor expressions are:

  1. (c2,c3) > (1,1)
  2. c2 > 1 OR ((c2 = 1) AND (c3 > 1))

Rewriting the query to use the nonconstructor expression results in the optimizer using all three columns in the index (key_len=12):

  1. mysql> EXPLAIN SELECT * FROM t1
  2.        WHERE c1 = 1 AND (c2 > 1 OR ((c2 = 1) AND (c3 > 1)))\G
  3. *************************** 1. row ***************************
  4.            id: 1
  5.   select_type: SIMPLE
  6.         table: t1
  7.    partitions: NULL
  8.          type: range
  9. possible_keys: PRIMARY
  10.           key: PRIMARY
  11.       key_len: 12
  12.           ref: NULL
  13.          rows: 3
  14.      filtered: 100.00
  15.         Extra: Using where

Thus, for better results, avoid mixing row constructors with AND/OR expressions. Use one or the other.

Under certain conditions, the optimizer can apply the range access method to IN() expressions that have row constructor arguments. See Range Optimization of Row Constructor Expressions.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-row-constructor-optimization.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut