diff options
| author | Mattias Jonsson <mattias.jonsson@sun.com> | 2008-11-05 15:53:28 +0100 |
|---|---|---|
| committer | Mattias Jonsson <mattias.jonsson@sun.com> | 2008-11-05 15:53:28 +0100 |
| commit | bcd88c9f9e617c4a9c426cbd0902f93a486e6b81 (patch) | |
| tree | 61c7646440805b1cc1792e0257e611e61c371156 /mysql-test/r/mysqlshow.result | |
| parent | c780c2a24ce4077c6fdf12c1af14d825fefa8a51 (diff) | |
| download | mariadb-git-bcd88c9f9e617c4a9c426cbd0902f93a486e6b81.tar.gz | |
Bug#40494: MYSQL server crashes on range access with partitioning and
order by
Problem was that the first index read was unordered,
and the next was ordered, resulting in use of
uninitialized data.
Solution was to use the correct variable to see if
the 'next' call should be ordered or not.
mysql-test/r/partition.result:
Bug#40494: MYSQL server crashes on range access with
partitioning and order by
Added test case for the bug.
mysql-test/t/partition.test:
Bug#40494: MYSQL server crashes on range access with
partitioning and order by
Added test case for the bug.
sql/ha_partition.cc:
Bug#40494: MYSQL server crashes on range access with
partitioning and order by
Used the wrong variable to decide to continue with
ordered or unordered scan.
Diffstat (limited to 'mysql-test/r/mysqlshow.result')
0 files changed, 0 insertions, 0 deletions