Alexander Barkov 1ae09ec863 Merge remote-tracking branch 'origin/10.4' into 10.5

2019-10-01 11:44:27 +04:00

..

alter_inplace-9045.result

…

binlog.result

Merge 10.1 into 10.2

2019-03-27 12:26:11 +02:00

charsets.result

…

cross_db.result

…

delayed.result

…

index.result

MDEV-16961 Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' failed upon concurrent DELETE and DDL with virtual blob column

2018-08-22 22:18:44 +02:00

innodb_autoinc_vcol.result

…

innodb_virtual_fk.result

…

load_data.result

…

mrr.result

…

myisam_repair_prefix_varchar.result

…

not_supported.result

…

partition.result

Merge 10.1 into 10.2

2019-03-27 12:26:11 +02:00

races.result

MDEV-17349 Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' failed on concurrent SELECT and DELETE after RENAME from table with index on virtual column

2018-11-04 08:12:28 +01:00

range.result

…

rpl_vcol.result

…

update_binlog.result

Merge branch '10.3' into 10.4

2019-09-06 11:53:10 +02:00

update.result

Merge branch '10.3' into 10.4

2019-09-06 11:53:10 +02:00

upgrade.result

MDEV-17909 Problem by MariaDB Update 10.1.32 -> 10.2.19 (Incorrect information in file: .frm)

2018-12-20 08:06:55 +01:00

vcol_archive.result

…

vcol_blackhole.result

…

vcol_blocked_sql_funcs.result

…

vcol_column_def_options_innodb.result

…

vcol_column_def_options_myisam.result

…

vcol_csv.result

…

vcol_handler_aria.result

…

vcol_handler_innodb.result

…

vcol_handler_myisam.result

…

vcol_ins_upd_innodb.result

Merge 10.1 into 10.2

2019-03-27 12:26:11 +02:00

vcol_ins_upd_myisam.result

Merge 10.1 into 10.2

2019-03-27 12:26:11 +02:00

vcol_keys_aria.result

…

vcol_keys_innodb.result

Merge 10.4 into 10.5

2019-09-17 09:07:52 +03:00

vcol_keys_myisam.result

Merge 10.3 into 10.4

2019-05-05 10:23:14 +03:00

vcol_memory.result

…

vcol_merge.result

…

vcol_misc.result

Merge 10.3 into 10.4

2019-06-19 10:49:00 +03:00

vcol_non_stored_columns_innodb.result

…

vcol_non_stored_columns_myisam.result

…

vcol_partition_innodb.result

…

vcol_partition_myisam.result

…

vcol_select_innodb.result

MDEV-16188 Post-merge corrections and adjustments

2019-02-04 22:44:33 -08:00

vcol_select_myisam.result

Merge 10.3 into 10.4

2019-06-12 08:37:27 +03:00

vcol_sql_mode_datetime.result

Merge 10.4 into 10.5

2019-09-24 10:07:56 +03:00

vcol_sql_mode_time.result

Merge 10.4 into 10.5

2019-09-24 10:07:56 +03:00

vcol_sql_mode_timestamp.result

Merge remote-tracking branch 'origin/10.4' into 10.5

2019-10-01 11:44:27 +04:00

vcol_sql_mode_upgrade.result

Revert "Part3: MDEV-18156 Assertion 0' failed or btr_validate_index(index, 0, false)' in row_upd_sec_index_entry or error code 126: Index is corrupted upon DELETE with PAD_CHAR_TO_FULL_LENGTH"

2019-09-11 13:52:33 +04:00

vcol_sql_mode.result

Merge 10.4 into 10.5

2019-09-17 09:07:52 +03:00

vcol_supported_sql_funcs.result

…

vcol_syntax.result

…

vcol_trigger_sp_innodb.result

MDEV-18156 Assertion 0' failed or btr_validate_index(index, 0, false)' in row_upd_sec_index_entry or error code 126: Index is corrupted upon DELETE with PAD_CHAR_TO_FULL_LENGTH

2019-09-03 05:34:53 +04:00

vcol_trigger_sp_myisam.result

MDEV-18156 Assertion 0' failed or btr_validate_index(index, 0, false)' in row_upd_sec_index_entry or error code 126: Index is corrupted upon DELETE with PAD_CHAR_TO_FULL_LENGTH

2019-09-03 05:34:53 +04:00

vcol_view_innodb.result

…

vcol_view_myisam.result

…

wrong_arena.result

MDEV-17563 Different results using table or view when comparing values of time type

2018-11-08 09:31:46 +04:00