diff options
| author | Vicențiu Ciorbaru <vicentiu@mariadb.org> | 2021-03-28 21:09:51 +0300 |
|---|---|---|
| committer | Vicențiu Ciorbaru <vicentiu@mariadb.org> | 2021-04-21 14:08:58 +0300 |
| commit | 2d595319bf542dcdeeb058139efa2ef54f645c7b (patch) | |
| tree | 0b1386cd1340b2a2c175f45f12d64e35e945e1b9 /mysql-test/main/fetch_first.test | |
| parent | 3fcc4f6fc24e8bde2f7d3a6aa162d69554bf8e6f (diff) | |
| download | mariadb-git-2d595319bf542dcdeeb058139efa2ef54f645c7b.tar.gz | |
cleanup: Select_limit_counters rename set_unlimited to clear
The function was originally introduced by eb0804ef5e7eeb059bb193c3c6787e8a4188d34d
MDEV-18553: MDEV-16327 pre-requisits part 1: isolation of LIMIT/OFFSET handling
set_unlimited had an overloaded notion of both clearing the offset value
and the limit value. The code is used for SQL_CALC_ROWS option to
disable the limit clause after the limit is reached, while at the same
time the calling code suppreses sending of rows.
Proposed solution:
Dedicated clear method for query initialization (to ensure no garbage
remains between executions).
Dedicated set_unlimited that only alters the limit value.
Diffstat (limited to 'mysql-test/main/fetch_first.test')
0 files changed, 0 insertions, 0 deletions