1
0
mirror of https://github.com/MariaDB/server.git synced 2026-10-23 18:49:29 +03:00
Files
mariadb/sql/sql_delete.h
Alexander Barkov 65fbc1dcdb MDEV-39563 Implement UPDATE ... RETURNING ... INTO
Adding support for UPDATE .. RETURNING .. INTO queries.

For example:

  UPDATE t1 SET a=10,b=20 RETURNING a,b INTO va,vb;
  UPDATE t1 SET a=10,b=20 RETURNING a,b INTO @a,@b;

Limitations:
1. These types of queries:
   - REPLACE .. RETURNING .. INTO
   - DELETE .. RETURNING .. INTO
   - INSERT .. RETURNING .. INTO
   do not work - they return an error.
   They will be implemented separately, when needed.

2. UPDATE..RETURNING..INTO with --binlog_format=statement is not allowed
   and an error is raised.

3. Using OLD_VALUE(col) inside UPDATE..RETURNING..INTO is not allowed
   and an error is raised.

4. Multi-table updates, as well as single table updates with a subquery
   to the same table in WHERE (which get converted to multi-table) do
   not work and an error is raised.

Notes:

1. ANALYZE and EXPLAIN
   Both
     ANALYZE UPDATE .. RETURNING .. INTO ..
     EXPLAIN UPDATE .. RETURNING .. INTO ..
   return this error:
     'RETURNING..INTO' is not allowed in this context

2. Behavior on no data

  a. In case of degenerated plans (WHERE 1=0, LIMIT 0),
     no errors are raised.

  b. If the updated table contains no rows, the behavior depends on the engine,
     for example:
     - MyISAM returns no errors
     - InnoDB raises
         No data - zero rows fetched, selected, or processed
     This behavior is engine dependent because some engines (e.g. MyISAM)
     quickly know that the table has no records and execute the statement
     using a degenerated plan.

  c. If there are some rows, but non of them match the WHERE condition,
     then this error is raised:
       No data - zero rows fetched, selected, or processed

  d. If some rows where found but none of them actually
     got changed by the SET, still this error is raised:
       No data - zero rows fetched, selected, or processed
     The error message might be misleading. However, if we read
     it as "zero rows [that required updates] fetched", it looks OK.
     Let's not introduce a new error message for now.

Helper changes:

1. The grammar in analyze_stmt_command was changed to have
   LEX::analyze_stmt set to true earlier, so
   LEX::set_returning_into_result() already knows if this
   is an ANALYZE statement.

2. The Sql_cmd_update constructor is now called earlier in the grammar,
   to be able to call Sql_cmd_update::set_with_old_value_items()
   in the SET and RETURNING clauses.

3. Sql_cmd_dml::lex is now set during the constructor time.
   It makes things easier:
   - Sql_cmd_update::returns_result_set() needs the lex.
   - Sql_cmd_delete::orig_multitable and Sql_cmd_update::orig_multitable
     are not needed any more.
     They were used only in Sql_cmd_delete::sql_command_code() and
     Sql_cmd_update::sql_command_code().
     Sql_cmd_dml::sql_command_code() now returns lex->sql_command.
     The overrides Sql_cmd_delete::sql_command_code() and
     Sql_cmd_update::sql_command_code() were removed.
2026-09-16 15:49:26 +02:00

116 lines
3.5 KiB
Objective-C

/* Copyright (c) 2006, 2010, Oracle and/or its affiliates. All rights reserved.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; version 2 of the License.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1335 USA */
#ifndef SQL_DELETE_INCLUDED
#define SQL_DELETE_INCLUDED
#include "my_base.h" /* ha_rows */
#include "sql_class.h" /* enum_duplicates */
#include "sql_cmd.h" // Sql_cmd_dml
#include "sql_base.h"
class THD;
struct TABLE_LIST;
class Item;
class select_result;
typedef class Item COND;
template <typename T> class SQL_I_List;
/**
@class Sql_cmd_delete - class used for any DELETE statements
This class is derived from Sql_cmd_dml and contains implementations
for abstract virtual function of the latter such as precheck() and
prepare_inner(). It also overrides the implementation of execute_inner()
providing a special handling for single-table delete statements that
are not converted to multi-table delete.
The class provides an object of the DML_prelocking_strategy class
for the virtual function get_dml_prelocking_strategy().
*/
class Sql_cmd_delete final : public Sql_cmd_dml
{
public:
ha_rows deleted{0};
Sql_cmd_delete(LEX *lex, bool multitable_arg)
: Sql_cmd_dml(lex),
multitable(multitable_arg),
save_protocol(NULL)
{}
/**
@brief Check if the statement returns a result set
*/
bool returns_result_set() const override
{
return returns_result_set_generic(lex);
}
DML_prelocking_strategy *get_dml_prelocking_strategy() override
{
return &multidelete_prelocking_strategy;
}
bool processing_as_multitable_delete_prohibited(THD *thd);
bool is_multitable() const { return multitable; }
void set_as_multitable() { multitable= true; }
void remove_order_by_without_limit(THD *thd);
void get_dml_stat (ha_rows &found, ha_rows &changed) override
{
found= 0;
changed= deleted;
}
protected:
/**
@brief Perform precheck of table privileges for delete statements
*/
bool precheck(THD *thd) override;
/**
@brief Perform context analysis for delete statements
*/
bool prepare_inner(THD *thd) override;
/**
@brief Perform optimization and execution actions needed for deletes
*/
bool execute_inner(THD *thd) override;
private:
/**
@biefSpecial handling of single-table deletes after prepare phase
*/
bool delete_from_single_table(THD *thd);
/*
True if the statement is a multitable delete or converted to such.
For a single-table delete this flag is set to true if the statement
is supposed to be converted to multi-table delete.
*/
bool multitable;
/* The prelocking strategy used when opening the used tables */
Multidelete_prelocking_strategy multidelete_prelocking_strategy;
List<Item> empty_list; /**< auxiliary empty list used by prepare_inner() */
Protocol *save_protocol; /**< needed for ANALYZE .. DELETE .. RETURNING */
};
#endif /* SQL_DELETE_INCLUDED */