diff options
| author | Jacob Mathew <jacob.mathew@mariadb.com> | 2018-09-13 11:41:55 -0700 |
|---|---|---|
| committer | Jacob Mathew <jacob.mathew@mariadb.com> | 2018-09-13 11:41:55 -0700 |
| commit | 38665893087e20c3ad65d5b0e227a75185a4865e (patch) | |
| tree | d52e91f7af23358e15314633b561cc48f923797a /storage/tokudb/mysql-test/tokudb/r/fast_update_binlog_row.result | |
| parent | 8e68876477eaec7944baa0b63ef26e551693c4f8 (diff) | |
| parent | eb2ca3d44586ebfb887ee54ea5e5275ee4b25623 (diff) | |
| download | mariadb-git-38665893087e20c3ad65d5b0e227a75185a4865e.tar.gz | |
MDEV-16912: Spider Order By column[datatime] limit 5 returns 3 rows
The problem occurs in 10.2 and earlier releases of MariaDB Server because the
Partition Engine was not pushing the engine conditions to the underlying
storage engine of each partition. This caused Spider to return the first 5
rows in the table with the data provided by the customer. 2 of the 5 rows
did not qualify the WHERE clause, so they were removed from the result set by
the server.
To fix the problem, I have back-ported support for engine condition pushdown
in the Partition Engine from MariaDB Server 10.3.
Author:
Jacob Mathew.
Reviewer:
Kentoku Shiba.
Merged:
Commit eb2ca3d on branch bb-10.2-MDEV-16912
Diffstat (limited to 'storage/tokudb/mysql-test/tokudb/r/fast_update_binlog_row.result')
0 files changed, 0 insertions, 0 deletions