mariadb/storage/innobase/btr
Marko Mäkelä 024a18dbcb MDEV-34823 Invalid arguments in ib_push_warning()
In the bug report MDEV-32817 it occurred that the function
row_mysql_get_table_status() is outputting a fil_space_t*
as if it were a numeric tablespace identifier.

ib_push_warning(): Remove. Let us invoke push_warning_printf() directly.

innodb_decryption_failed(): Report a decryption failure and set the
dict_table_t::file_unreadable flag. This code was being duplicated in
very many places. We return the constant value DB_DECRYPTION_FAILED
in order to avoid code duplication in the callers and to allow tail calls.

innodb_fk_error(): Report a FOREIGN KEY error.

dict_foreign_def_get(), dict_foreign_def_get_fields(): Remove.
This code was being used in dict_create_add_foreign_to_dictionary()
in an apparently uncovered code path. That ib_push_warning() call
would pass the integer i+1 instead of a pointer to NUL terminated
string ("%s"), and therefore the call should have resulted in a crash.

dict_print_info_on_foreign_key_in_create_format(),
innobase_quote_identifier(): Add const qualifiers.

row_mysql_get_table_error(): Replaces row_mysql_get_table_status().
Display no message on DB_CORRUPTION; it should be properly reported at
the SQL layer anyway.
2024-09-06 14:29:09 +03:00
..
btr0btr.cc MDEV-34823 Invalid arguments in ib_push_warning() 2024-09-06 14:29:09 +03:00
btr0bulk.cc Merge branch '10.4' into 10.5 2024-01-31 17:32:53 +01:00
btr0cur.cc MDEV-34823 Invalid arguments in ib_push_warning() 2024-09-06 14:29:09 +03:00
btr0defragment.cc Merge 10.4 into 10.5 2022-12-13 14:39:18 +02:00
btr0pcur.cc MDEV-32489 Change buffer index fails to delete the records 2024-04-18 08:30:21 +05:30
btr0sea.cc Merge 10.4 into 10.5 2022-12-13 14:39:18 +02:00