breakpoints#1080 41 2.2.4 Bug Fixes • TiDB – Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 – Fix the issue of wrong query results statement, executing DDL statements, or modifying the value of SQL mode / time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache execution plan that is specific to current parameter values; 619 • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory

statement, executing DDL statements, or modifying the value of SQL mode / time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory breakpoints#1080 2678 14.5.6.4 Bug Fixes • TiDB – Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 – Fix the issue of wrong query results

statement, executing DDL statements, or modifying the value of SQL mode / time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache execution plan that is specific to current parameter values; 640 • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory breakpoints#1080 2530 14.4.6.4 Bug Fixes • TiDB – Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 – Fix the issue of wrong query results

statement, executing DDL statements, or modifying the value of SQL mode / time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory breakpoints#1080 3331 14.7.6.4 Bug Fixes • TiDB – Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 – Fix the issue of wrong query results

statement, executing DDL statements, or modifying the value of SQL mode / time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache execution plan that is specific to current parameter values; 1302 • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory breakpoints#1080 4167 16.10.6.4 Bug Fixes • TiDB • Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 • Fix the issue of wrong query results

statement, executing DDL statements, or modifying the value of SQL mode/time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory scan when IndexLookup involves many table retrieval tasks #45132 @qw4990 • Optimize the join elimination rule to improve the query performance of join on �→ unique keys #46248 @fixdb • Change the collation

statement, executing DDL statements, or modifying the value of SQL mode/time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory scan when IndexLookup involves many table retrieval tasks #45132 @qw4990 • Optimize the join elimination rule to improve the query performance of join on �→ unique keys #46248 @fixdb • Change the collation

statement, executing DDL statements, or modifying the value of SQL mode / time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory breakpoints#1080 4961 16.14.6.4 Bug Fixes • TiDB • Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 • Fix the issue of wrong query results

statement, executing DDL statements, or modifying the value of SQL mode/time_zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory #1080 5395 16.17.6.4 Bug Fixes • TiDB • Fix the issue that the execution result of project elimination might be wrong when the projection result is empty #23887 • Fix the issue of wrong query results

executing DDL statements, or modifying the value of SQL mode/time �→ _zone), or the LRU cache elimination mechanism causes the execution plan cache miss when executing. After the execution plan cache TableDual execution plan that is specific to current parameter values; • If cache invalidation and elimination are not considered, an execution plan cache is applied to various parameter values, which in theory scan when IndexLookup involves many table retrieval tasks #45132 @qw4990 • Optimize the join elimination rule to improve the query performance of join on �→ unique keys #46248 @fixdb • Change the collation