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_delete.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_delete.cc')
| -rw-r--r-- | sql/sql_delete.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sql/sql_delete.cc b/sql/sql_delete.cc index a965a7115d2..4488b4a92dd 100644 --- a/sql/sql_delete.cc +++ b/sql/sql_delete.cc @@ -815,6 +815,7 @@ bool mysql_delete(THD *thd, TABLE_LIST *table_list, COND *conds, break; } + // no LIMIT / OFFSET if (with_select && result->send_data(select_lex->item_list) < 0) { error=1; |