diff options
author | Oleksandr Byelkin <sanja@mariadb.com> | 2019-10-11 12:26:15 +0200 |
---|---|---|
committer | Oleksandr Byelkin <sanja@mariadb.com> | 2019-10-13 09:40:41 +0200 |
commit | 1ae02f0e0d28bfca037ec35c4fda5b01c853b09f (patch) | |
tree | 13af954bcd05c91a9a937d675c28f2e16e9ef9af /sql/sql_profile.cc | |
parent | eb0804ef5e7eeb059bb193c3c6787e8a4188d34d (diff) | |
download | mariadb-git-1ae02f0e0d28bfca037ec35c4fda5b01c853b09f.tar.gz |
MDEV-18553: MDEV-16327 pre-requisits part 2: uniform of LIMIT/OFFSET handling
Now both offset and limit are stored and do not chenged during execution
(offset is decreased during processing in versions before 10.5).
(Big part of this changes made by Monty)
Diffstat (limited to 'sql/sql_profile.cc')
-rw-r--r-- | sql/sql_profile.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/sql_profile.cc b/sql/sql_profile.cc index 40e7908ac1d..cee55761a98 100644 --- a/sql/sql_profile.cc +++ b/sql/sql_profile.cc @@ -436,7 +436,7 @@ bool PROFILING::show_profiles() double query_time_usecs= prof->m_end_time_usecs - prof->m_start_time_usecs; - if (unit->lim.check_and_move_offset()) + if (unit->lim.check_offset(idx)) continue; if (idx > unit->lim.get_select_limit()) break; |