diff options
| author | unknown <sergefp@mysql.com> | 2007-11-20 05:02:49 +0300 |
|---|---|---|
| committer | unknown <sergefp@mysql.com> | 2007-11-20 05:02:49 +0300 |
| commit | 861a18b9a94f63ad7a5349d7d3dc7c1694ec8db5 (patch) | |
| tree | bece4a64380034d28f6208449edb115f8b306f12 /mysql-test/t/overflow.test | |
| parent | 8d1b43b14d2b50cb58b0d60de19d75e902544703 (diff) | |
| download | mariadb-git-861a18b9a94f63ad7a5349d7d3dc7c1694ec8db5.tar.gz | |
BUG#30573: Ordered range scan over partitioned tables returns some rows twice
The problem: ha_partition::read_range_first() could return a record that is
outside of the scanned range. If that record happened to be in the next
subsequent range, it would satisfy the WHERE and appear in the output twice.
(we would get it the second time when scanning the next subsequent range)
Fix:
Made ha_partition::read_range_first() check if the returned recod is within
the scanned range, like other read_range_first() implementations do.
mysql-test/r/partition_range.result:
BUG#30573: Ordered range scan over partitioned tables returns some rows twice
- Testcase
mysql-test/t/partition_range.test:
BUG#30573: Ordered range scan over partitioned tables returns some rows twice
- Testcase
sql/ha_partition.cc:
BUG#30573: Ordered range scan over partitioned tables returns some rows twice
- Make ha_partition::read_range_first() check if the returned record is
within the range.
Diffstat (limited to 'mysql-test/t/overflow.test')
0 files changed, 0 insertions, 0 deletions