summaryrefslogtreecommitdiff
path: root/storage/innobase/trx/trx0trx.cc
diff options
context:
space:
mode:
authorMonty <monty@mariadb.org>2021-03-22 16:05:08 +0200
committerSergei Golubchik <serg@mariadb.org>2021-05-19 22:54:13 +0200
commit3c578b0a960ce3f625b8e24c4c7605cec74e0154 (patch)
tree340b602150396509eabd2571439105823db58c14 /storage/innobase/trx/trx0trx.cc
parentc844a76b0aa79f763e87b50663e97a2a135be457 (diff)
downloadmariadb-git-3c578b0a960ce3f625b8e24c4c7605cec74e0154.tar.gz
Check if we can rename triggers before doing an ALTER TABLE ... RENAME
ALTER TABLE .. RENAME, when used with the inplace algorithm, does: - Do an inplace or online alter to the new definition - Rename to new name - Update triggers. If update triggers would fail, we would rename the table back. The problem with this approach is that the table would have the new definition but the rename would fail. The binary log would also not be updated. The solution to this is to very early check if we can rename triggers and give an error if this would fail. Both ALTER TABLE ... RENAME and RENAME TABLE is fixed. This was implemented by moving the pre-check of rename table in triggers from Table_triggers_list::change_table_name() to Table_triggers_list::prepare_for_rename().
Diffstat (limited to 'storage/innobase/trx/trx0trx.cc')
0 files changed, 0 insertions, 0 deletions