Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
69795 | 2013-07-19 17:54 | 2016-06-16 20:32 | MySQL Server: Optimizer | Verified (2842 days) | S3 | 5.6.12 | Any | Any | EXPLAIN FORMAT=JSON doesn't show Using filesort for UNIONs |
70014 | 2013-08-13 13:34 | 2013-11-19 16:31 | MySQL Server: Optimizer | Closed (3782 days) | S2 | 5.6.12-debug, 5.6.13-debug , 5.7.2-m12-enterprise-commercial-advanced-debug | Linux (Fedora 18) | Any | MySQL crashes on explain with JSON formatting (debug builds) |
71980 | 2014-03-08 19:44 | 2014-05-14 1:34 | MySQL Workbench: SQL Editor | Closed (3606 days) | S3 | 6.1.2.11661 | Any | Any | canvas too small for visual explain in export |
71973 | 2014-03-07 13:28 | 2014-05-14 23:41 | MySQL Workbench: SQL Editor | Closed (3606 days) | S3 | 6.1.2.11661 | Any | Any | Visual explain fails on large explain plan |
72265 | 2014-04-07 16:59 | 2014-04-08 4:56 | MySQL Enterprise Monitor: Agent | Verified (3642 days) | S3 | 3.0.8 | Any | Any | MEM tries to explain INSERT/UPDATE/DELETE type statements on a read-only slave |
73258 | 2014-07-10 11:19 | 2014-07-10 12:27 | MySQL Server: Security: Privileges | Verified (3549 days) | S3 | >= 5.6.3, 5.6.20 | Linux | Any | Unable to analyze ALL queries with EXPLAIN on read-only account |
73305 | 2014-07-17 7:27 | 2017-05-15 12:39 | MySQL Server: Documentation | Closed (2509 days) | S2 | 5.6, 5.7 | Any | Any | Manual does not explain all cases when SHOW VIEW privilege is needed |
73306 | 2014-07-17 7:35 | 2017-05-15 12:37 | MySQL Server: Documentation | Closed (2509 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Manual does not explain what privileges are needed for EXPLAIN explainable_stmt |
68871 | 2013-04-05 7:32 | 2014-08-27 4:36 | MySQL Server: Optimizer | Can't repeat (3501 days) | S3 | 5.1.58, 5.5.30, 5.6.10 | Any | Any | EXPLAIN does not show real plan used for query with HAVING |
72031 | 2014-03-13 8:22 | 2014-03-13 11:14 | MySQL Server: Optimizer | Verified (3668 days) | S3 | 5.6.16 | Any | Any | Strange explain behaviour |
71981 | 2014-03-08 20:24 | 2014-03-13 11:15 | MySQL Server: DML | Verified (3668 days) | S3 | 5.6.16 | Any | Any | Strange result on explain |
78213 | 2015-08-25 20:03 | 2015-10-23 12:55 | MySQL Server: Optimizer | Closed (3095 days) | S2 | 5.6, 5.6.26, 5.5.46, 5.1.77 | Any (Mac OS X 10.9 and CentOS 6) | Any | Spatial index causes incorrect cardinality for all non-primary indexes |
78943 | 2015-10-23 13:52 | 2015-10-26 7:19 | MySQL Server: Optimizer | Not a Bug (3076 days) | S3 | 5.6.24-72.2-log, 5.6.27 | Ubuntu (14.04) | Any | EXPLAIN FORMAT="JSON" ignores FORCE INDEX for some output parts |
79717 | 2015-12-21 2:47 | 2016-02-26 0:13 | MySQL Server: Documentation | Closed (2953 days) | S3 | 5.7 | Any | Any | Document Bug about "EXPLAIN Output Format" |
68912 | 2013-04-10 1:38 | 2013-05-17 1:00 | MySQL Workbench | No Feedback (3969 days) | S3 | 5.2.42 Rev 9752 | Windows | Any | Highlight text in the SQL Editor, EXPLAIN function runs against all text |
83062 | 2016-09-20 13:18 | 2018-04-24 20:15 | MySQL Server: Optimizer | Verified (2745 days) | S3 | 5.6.32, 5.7.14, 5.6.33, 5.7.15 | Any | Any | it's no longer possible to determine used key parts by looking at key_length |
72030 | 2014-03-13 7:45 | 2016-11-05 9:43 | MySQL Enterprise Monitor: Server | Not a Bug (2700 days) | S3 | 3.0.7 | Any | Any | Exceptions on SQL Explain |
83398 | 2016-10-16 11:09 | 2017-02-17 18:00 | MySQL Server: Documentation | Closed (2596 days) | S3 | 5.7.15 | Any | Any | Slow and unexpected explain output on FTS |
86897 | 2017-07-02 13:15 | 2017-07-02 18:26 | MySQL Workbench: SQL Editor | Duplicate (2461 days) | S3 | 6.3.6 | Windows (Microsoft Windows 10 Home) | Any | invalid literal for int() with base 10 |
86574 | 2017-06-03 16:16 | 2017-06-03 19:36 | MySQL Server: Optimizer | Verified (2490 days) | S3 | 5.6 | Any | Any | Confusing EXPLAIN output for INSERT Queries |
78412 | 2015-09-11 16:17 | 2017-01-13 9:03 | MySQL Server: Documentation | Closed (3030 days) | S2 | 5.6.24 | Any | Any | UPDATE with subquery is NOT optimized the same way as equivalent SELECT |
88817 | 2017-12-07 14:26 | 2018-01-19 11:17 | MySQL Server | Not a Bug (2260 days) | S3 | 5.7.17 | Linux (AWS RDS) | Any | Field or reference of SELECT #2 was resolved in SELECT #1 |
89047 | 2017-12-23 20:01 | 2023-02-02 20:53 | MySQL Workbench: SQL Editor | Verified (2128 days) | S3 | 6.3.10 and 8.0.11RC | MacOS (macOS 10.13.x High Sierra x86_64) | Any | Visual explain tooltip cropped |
99707 | 2020-05-27 12:33 | 2020-06-01 12:29 | MySQL Server: Documentation | Closed (1396 days) | S3 | 8.0.20, 5.7.30 | Any | Any | EXPLAIN requires more than SELECT |
106838 | 2022-03-25 11:30 | 2022-03-25 12:03 | MySQL Workbench | Verified (734 days) | S3 | 8.0.28 | MacOS (11.1) | Any | hover tooltip is cut when using query explain tab |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (405 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
111580 | 2023-06-27 11:01 | 2023-06-28 13:40 | MySQL Server: Security: Privileges | Not a Bug (274 days) | S3 | 8.0, 8.0.31 | Any | Any | view CREATE with SQL SECURITY DEFINER can SELECT but cannot EXPLAIN |
111564 | 2023-06-26 12:33 | 2023-08-10 12:21 | MySQL Server: Optimizer | Closed (231 days) | S3 | 8.0 | Any | Any | Contribution by Tencent: explain format=tree lost the subquery in the hash join |
50168 | 2010-01-08 2:16 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5188 days) | S3 | 5.0,5.1 | Any | Any | The value of 'rows' in EXPLAIN output is not accurate for LIMIT |
22413 | 2006-09-16 13:59 | 2006-11-27 18:19 | MySQL Server | Closed (6331 days) | S1 | 5.0.24a,5.0BK,5.1BK | Any | EXPLAIN SELECT FROM view with ORDER BY yield server crash |
Showing 1-30 of 55 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |