mariadb/mysql-test/suite/s3
Sergei Golubchik b5f50e2de8 errors after altering a table has finished aren't fatal
We cannot revert the ALTER, so anything happening after
the point of no return should not be treated as an error. A
very unfortunate condition that a user needs to be warned about - yes,
but we cannot say "ALTER TABLE has failed" if the table was successfully
altered.
2021-07-02 16:44:00 +02:00
..
alter.result errors after altering a table has finished aren't fatal 2021-07-02 16:44:00 +02:00
alter.test errors after altering a table has finished aren't fatal 2021-07-02 16:44:00 +02:00
alter2.result
alter2.test
amazon.result
amazon.test
arguments.result
arguments.test
backup.result
backup.test
basic.result
basic.test
create_database.inc
disabled.def
discovery.result
discovery.test
drop_database.inc
encryption.opt
encryption.result
encryption.test
innodb.result
innodb.test
my.cnf
mysqldump.result
mysqldump.test
no_s3-master.opt
no_s3.result
no_s3.test
partition.result
partition.test
partition_create_fail.result
partition_create_fail.test
partition_move.result
partition_move.test
replication.inc
replication_delayed.cnf
replication_delayed.result
replication_delayed.test
replication_mixed.cnf
replication_mixed.result
replication_mixed.test
replication_partition.cnf
replication_partition.result
replication_partition.test
replication_stmt.cnf
replication_stmt.result
replication_stmt.test
select.result
select.test
slave.cnf
suite.pm
unsupported.result
unsupported.test