summaryrefslogtreecommitdiff
path: root/mysql-test/main/mysqldump.result
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.5 into 10.6Marko Mäkelä2023-01-031-0/+1
|\
| * Merge 10.4 into 10.5Marko Mäkelä2023-01-031-0/+1
| |\
| | * Merge 10.3 into 10.4Marko Mäkelä2023-01-031-0/+1
| | |\
| | | * MDEV-30233 DROP DATABASE test fails: Directory not emptyMarko Mäkelä2022-12-151-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some tests drop the default mtr database "test". This may fail due to the directory not being empty. InnoDB may not delete all tables immediately, due to the "background drop table queue" or its replacement in commit 1bd681c8b3c5213ce1f7976940a7dc38b48a0d39 (the purge of history would clean up after a DDL operation during which the server was killed). Let us try to avoid "drop database test" whenever it is easily possible. Where it is not, SET GLOBAL innodb_max_purge_lag_wait=0 will ensure that the replacement of the "background drop table queue" will have completed its job.
* | | | Merge 10.5 into 10.6Marko Mäkelä2022-10-251-41/+41
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | To prevent ASAN heap-use-after-poison in the MDEV-16549 part of ./mtr --repeat=6 main.derived the initialization of Name_resolution_context was cleaned up.
| * | | MDEV-29615 mtr to use mariadb namesDaniel Black2022-10-211-41/+41
| | | |
* | | | Merge branch '10.5' into 10.6Sergei Golubchik2022-10-021-0/+16
|\ \ \ \ | |/ / /
| * | | Merge branch '10.4' into 10.5Sergei Golubchik2022-10-021-0/+16
| |\ \ \ | | |/ /
| | * | Merge branch '10.3' into 10.4Sergei Golubchik2022-10-011-0/+16
| | |\ \ | | | |/
| | | * cleanup: main.mysqldump testSergei Golubchik2022-09-261-0/+16
| | | | | | | | | | | | | | | | show error messages from mysqldump/mysqlimport
* | | | Merge 10.5 into 10.6Marko Mäkelä2022-09-201-129/+129
|\ \ \ \ | |/ / /
| * | | Merge remote-tracking branch 'origin/10.4' into 10.5Alexander Barkov2022-09-141-129/+129
| |\ \ \ | | |/ /
| | * | Merge 10.3 into 10.4Marko Mäkelä2022-09-131-129/+129
| | |\ \ | | | |/
| | | * MDEV-29446 Change SHOW CREATE TABLE to display default collationAlexander Barkov2022-09-121-129/+129
| | | |
* | | | Merge branch '10.5' into 10.6Oleksandr Byelkin2022-08-041-72/+45
|\ \ \ \ | |/ / /
| * | | Merge branch '10.4' into 10.5Oleksandr Byelkin2022-08-041-72/+45
| |\ \ \ | | |/ /
| | * | Merge branch '10.3' into 10.4Oleksandr Byelkin2022-08-031-72/+45
| | |\ \ | | | |/
| | | * MDEV-26447: mysqldump to use temporary view instead of tables.Daniel Black2022-08-031-72/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is particularly important for Azure where there is no MyISAM support in their MariaDB cloud product. Like mysqldumper does, a view can satisfy the requirement like a table, without constraints. The views in frm files are text form and don't have column limits. Thanks Thomas Casteleyn for the suggestion.
* | | | Merge branch '10.5' into 10.6Sergei Golubchik2022-05-101-100/+215
|\ \ \ \ | |/ / /
| * | | Merge branch '10.4' into 10.5Sergei Golubchik2022-05-091-100/+215
| |\ \ \ | | |/ /
| | * | Merge branch '10.3' into 10.4Sergei Golubchik2022-05-081-100/+215
| | |\ \ | | | |/
| | | * MDEV-4875 Can't restore a mysqldump if --add-drop-database meets general_logDaniel Black2022-05-061-86/+180
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | or slow query log when the log_output=TABLE. When this happens, we temporary disable by changing log_output until we've created the general_log and slow_log tables again. Move </database> in xml mode until after the transaction_registry. General_log and slow_log tables where moved to be first to be dumped so that the disabling of the general/slow queries is minimal.
| | | * MDEV-27816 Set sql_mode before DROP IF EXISTS alreadyHartmut Holzgraefe2022-05-061-14/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the correct SQL mode for a stored routine or package was only set before doing the CREATE part, this worked out for PROCEDUREs and FUNCTIONs, but with ORACLE mode specific PACKAGEs the DROP also only works in ORACLE mode. Moving the setting of the sql_mode a few lines up to happen right before the DROP statement is writen fixes this.
| | * | Merge branch '10.3' into 10.4Oleksandr Byelkin2022-01-301-23/+23
| | |\ \ | | | |/
| | | * MDEV-18918 SQL mode EMPTY_STRING_IS_NULL breaks RBR upon CREATE TABLE .. SELECTAlexander Barkov2022-01-251-23/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removing DEFAULT from INFORMATION_SCHEMA columns. DEFAULT in read-only tables is rather meaningless. Upgrade should go smoothly. Also fixes: MDEV-20254 Problems with EMPTY_STRING_IS_NULL and I_S tables
* | | | Merge branch '10.5' into 10.6Oleksandr Byelkin2022-02-031-23/+23
|\ \ \ \ | |/ / /
| * | | MDEV-18918 SQL mode EMPTY_STRING_IS_NULL breaks RBR upon CREATE TABLE .. SELECTAlexander Barkov2022-01-251-23/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The 10.5 version of the patch. Removing DEFAULT from INFORMATION_SCHEMA columns. DEFAULT in read-only tables is rather meaningless. Upgrade should go smoothly. Also fixes: MDEV-20254 Problems with EMPTY_STRING_IS_NULL and I_S tables
* | | | Merge branch '10.5' into 10.6Oleksandr Byelkin2021-08-021-0/+1
|\ \ \ \ | |/ / /
| * | | MDEV-25908: -e does not work for my_print_defaultsRucha Deodhar2021-07-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Analysis: get_defaults_options() rewrites the value for my_defaults_file, my_defaults_extra_file and my_defaults_group_suffix to 0. So the config file can't be read. Fix: Let handle_options() handle --defaults* option and create a new command line to pass it to load_defaults().
* | | | MDEV-8334: Rename utf8 to utf8mb3Rucha Deodhar2021-05-191-77/+77
| | | | | | | | | | | | | | | | | | | | | | | | This patch changes the main name of 3 byte character set from utf8 to utf8mb3. New old_mode UTF8_IS_UTF8MB3 is added and set TRUE by default, so that utf8 would mean utf8mb3. If not set, utf8 would mean utf8mb4.
* | | | MDEV-7317: Make an index ignorable to the optimizerVarun Gupta2021-03-041-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This feature adds the functionality of ignorability for indexes. Indexes are not ignored be default. To control index ignorability explicitly for a new index, use IGNORE or NOT IGNORE as part of the index definition for CREATE TABLE, CREATE INDEX, or ALTER TABLE. Primary keys (explicit or implicit) cannot be made ignorable. The table INFORMATION_SCHEMA.STATISTICS get a new column named IGNORED that would store whether an index needs to be ignored or not.
* | | Merge branch 'bb-10.4-release' into bb-10.5-releaseSergei Golubchik2021-02-151-5/+310
|\ \ \ | |/ /
| * | Merge branch 'bb-10.3-release' into bb-10.4-releaseSergei Golubchik2021-02-121-5/+310
| |\ \ | | |/ | | | | | | | | | Note, the fix for "MDEV-23328 Server hang due to Galera lock conflict resolution" was null-merged. 10.4 version of the fix is coming up separately
| | * main.mysqldump test isn't that bigSergei Golubchik2021-02-011-5/+1
| | | | | | | | | | | | and it is that important to be run every time
| | * Merge branch '10.2' into 10.3Sergei Golubchik2021-02-011-0/+309
| | |
* | | Merge 10.4 into 10.5Marko Mäkelä2020-11-031-2/+3
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-11-031-2/+3
| |\ \ | | |/
| | * Merge 10.2 into 10.3Marko Mäkelä2020-11-021-2/+3
| | |
* | | Merge 10.4 into 10.5Marko Mäkelä2020-10-301-0/+118
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-10-291-0/+118
| |\ \ | | |/
| | * MDEV-21786 mysqldump will forget sequence definition details on --no-data dumpAnel Husakovic2020-10-231-0/+118
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Original patch was contributed by Jani Tolonen <jani.k.tolonen@gmail.com> https://github.com/an3l/server/commits/bb-10.3-anel-MDEV-21786-dump-sequence which distinguishes data structure (linked list) of sequences from tables. - Added standard sql output to prevent future changes of sequences and disabled locks for sequences. - Added test case for `MDEV-20070: mysqldump won't work correct on sequences` where table column depends on sequence value. - Restore sequence last value in the following way: - Find `next_not_cached_value` and use it to `setval()` - We just need for logical restore, so don't execute `setval()` - `setval()` should be showed also in case of `--no-data` option. Reviewed-by: daniel@mariadb.org
* | | Merge 10.4 into 10.5Marko Mäkelä2020-05-311-1/+1
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-05-261-1/+1
| |\ \ | | |/
| | * Merge 10.2 into 10.3Marko Mäkelä2020-05-251-1/+1
| | |
* | | Merge 10.4 into 10.5Marko Mäkelä2020-04-251-2/+22
|\ \ \ | |/ / | | | | | | | | | The functional changes of commit 5836191c8f0658d5d75484766fdcc3d838b0a5c1 (MDEV-21168) are omitted due to MDEV-742 having addressed the issue.
| * | Merge 10.3 into 10.4Marko Mäkelä2020-04-161-2/+22
| |\ \ | | |/ | | | | | | | | | | | | | | | In main.index_merge_myisam we remove the test that was added in commit a2d24def8cc42d27c72d833abfb39ef24a2b96ba because it duplicates the test case that was added in commit 5af12e463549e4bbc2ce6ab720d78937d5e5db4e.
| | * Merge 10.2 into 10.3Marko Mäkelä2020-04-151-2/+22
| | |
* | | MDEV-21743: Re-record --big-test resultsMarko Mäkelä2020-03-111-2/+2
| | |
* | | Fixed wrong result files in test suiteMonty2019-10-301-1/+0
|/ /
* | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-05-191-0/+34
|\ \ | |/