diff options
author | unknown <andrey@example.com> | 2006-08-28 10:27:42 +0200 |
---|---|---|
committer | unknown <andrey@example.com> | 2006-08-28 10:27:42 +0200 |
commit | f18ec676a0b0be35068e2c464b39d92ac143ec5c (patch) | |
tree | 20f1308446168c71113bc7ef963c8dfb57bd5188 /sql/event_db_repository.cc | |
parent | bd868fb60cb9aa47a3add210d11bb4b2d5b7eed7 (diff) | |
download | mariadb-git-f18ec676a0b0be35068e2c464b39d92ac143ec5c.tar.gz |
WL#3337 (Event scheduler new architecture)
Don't send affected rows after CREATE/ALTER/DROP EVENT as this is
inconsistent with the rest of the server in terms of CREATE/ALTER/DROP
DDLs
sql/event_data_objects.cc:
Events::drop_event() does not expect anymore a parameter named affected_rows
sql/event_db_repository.cc:
Remove rows_affected as the behavior exposed by Events is not
coherent with the behavior of many other DDL, like CREATE PROCEDURE, etc.
sql/event_db_repository.h:
Remove rows_affected as the behavior exposed by Events is not
coherent with the behavior of many other DDL, like CREATE PROCEDURE, etc.
sql/events.cc:
Remove rows_affected as the behavior exposed by Events is not
coherent with the behavior of many other DDL, like CREATE PROCEDURE, etc.
sql/events.h:
Remove rows_affected as the behavior exposed by Events is not
coherent with the behavior of many other DDL, like CREATE PROCEDURE, etc.
sql/sql_parse.cc:
Don't send affected rows, because this behavior is not consistent
with the rest of the server for CREATE/ALTER/DROP DDLs
Diffstat (limited to 'sql/event_db_repository.cc')
-rw-r--r-- | sql/event_db_repository.cc | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/sql/event_db_repository.cc b/sql/event_db_repository.cc index c6b84a1c84b..69f44b44be0 100644 --- a/sql/event_db_repository.cc +++ b/sql/event_db_repository.cc @@ -508,7 +508,6 @@ check_parse_params(THD *thd, Event_parse_data *parse_data) thd [in] THD parse_data [in] Object containing info about the event create_if_not [in] Whether to generate anwarning in case event exists - rows_affected [out] How many rows were affected RETURN VALUE 0 OK @@ -521,7 +520,7 @@ check_parse_params(THD *thd, Event_parse_data *parse_data) bool Event_db_repository::create_event(THD *thd, Event_parse_data *parse_data, - my_bool create_if_not, uint *rows_affected) + my_bool create_if_not) { int ret= 0; CHARSET_INFO *scs= system_charset_info; @@ -532,7 +531,6 @@ Event_db_repository::create_event(THD *thd, Event_parse_data *parse_data, DBUG_ENTER("Event_db_repository::create_event"); - *rows_affected= 0; if (check_parse_params(thd, parse_data)) goto err; @@ -621,7 +619,6 @@ Event_db_repository::create_event(THD *thd, Event_parse_data *parse_data, goto err; } - *rows_affected= 1; ok: if (dbchanged) (void) mysql_change_db(thd, old_db.str, 1); @@ -760,7 +757,6 @@ err: name [in] Event's name drop_if_exists [in] If set and the event not existing => warning onto the stack - rows_affected [out] Affected number of rows is returned heres RETURN VALUE FALSE OK @@ -769,7 +765,7 @@ err: bool Event_db_repository::drop_event(THD *thd, LEX_STRING db, LEX_STRING name, - bool drop_if_exists, uint *rows_affected) + bool drop_if_exists) { TABLE *table= NULL; Open_tables_state backup; |