| Bug #105694 | A typo issue in TABLE_LIST::save_properties() | ||
|---|---|---|---|
| Submitted: | 24 Nov 2021 11:46 | Modified: | 29 Nov 2021 22:33 |
| Reporter: | Hope Lee (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: DML | Severity: | S3 (Non-critical) |
| Version: | 8.0.27 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[24 Nov 2021 12:01]
MySQL Verification Team
Hello Lee, Thank you for the report and contributions. regards, Umesh
[24 Nov 2021 12:05]
MySQL Verification Team
8.0.27 ====== https://github.com/mysql/mysql-server/blob/8.0/sql/table.cc#L4447 I could be wrong but looks like this was introduced after WL#9384: Prepare each DML statement once
[24 Nov 2021 12:07]
MySQL Verification Team
################ 5.7 - NA I could not locate and moreover this seems to be introduced after WL#9384
[29 Nov 2021 22:33]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL 8.0.28 release, and here's the proposed changelog entry from the documentation team: Incorrect values for FORCE INDEX FOR GROUP BY could be set while saving and restoring the presence of FORCE INDEX hints within tables. Thank you for the bug report.
Description: A typo issue in TABLE_LIST::save_properties(). How to repeat: diff --git a/sql/table.cc b/sql/table.cc index 2b98412e40c..c6191b404c1 100644 --- a/sql/table.cc +++ b/sql/table.cc @@ -4444,7 +4444,7 @@ bool TABLE_LIST::save_properties() { nullable_saved = table->is_nullable(); force_index_saved = table->force_index; force_index_order_saved = table->force_index_order; - force_index_group_saved = table->force_index_order; + force_index_group_saved = table->force_index_group; partition_info *const part = table->part_info; if (part != nullptr) { const uint part_count = part->read_partitions.n_bits;