summaryrefslogtreecommitdiff
path: root/mysql-test
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-8475 stale .TMM file causes MyiSAM and Aria engine to stop serving the ↵Monty2015-08-184-5/+130
| | | | | | | | table Issue was two fold (both in MyISAM and Aria) - optimize and repair failed if there was an old .TMM file around. As optimized and repair are protected against multiple execution, I decided to change so that we just truncate the file if it exists. - I had missed to check for error condition if creation of the temporary index file failed. This caused the strange behaviour that it looked as if optimized would have worked once.
* MDEV-5096 - Wrong error message on attempt to kill somebody else's query IDSergey Vojtovich2015-07-242-0/+38
| | | | | Attempting to kill query owned by different user now returns better error: "You are not owner of query N" instead of "You are not owner of thread N".
* Merge branch 'bb-10.1-serg' into 10.1mariadb-10.1.6Sergei Golubchik2015-07-231-128/+128
|\
| * fix for 32-bit testsSergei Golubchik2015-07-221-128/+128
| |
* | MDEV-8501: encryption.create_or_replace fails in buildbot on P8 buildersJan Lindström2015-07-211-0/+2
|/ | | | | | | | | | | | Analysis: There is race between drop table and encryption threads that could cause encryption thread to enter mutex that has been already released. Fix: When destroying crypt_data first enter the mutex and set crypt data unavailable, then release the memory and clean up the data. This should make the race more unprobable. Additionally, added big_test for create_or_replace as it could fail testcase timeout if you have slow I/O (tested that testcase passes with --mem).
* MDEV-8500 sys_vars.sysvars_innodb '32bit,xtradb' failsElena Stepanova2015-07-201-2/+2
| | | | The version in sysvars_innodb,32bit,xtradb.rdiff was not updated
* Merge MDEV-8496 into 10.1Kristian Nielsen2015-07-192-0/+67
|\
| * MDEV-8496: gtid_ignore_duplicates treats gtid_seq_no as 32-bitKristian Nielsen2015-07-192-0/+67
| | | | | | | | | | --gtid-ignore-duplicates was comparing sequence numbers as 32-bit, so after 2**32 transactions things would start to fail.
* | MDEV-8495 encryption.innodb_first_page fails sporadically in buildbotElena Stepanova2015-07-171-0/+2
| | | | | | | | The test did not wait until the server shuts down
* | MDEV-8469 Add RESET MASTER TO x to allow specification of binlog file nrMonty2015-07-162-0/+21
| | | | | | | | | | | | | | | | Other things: - Avoid calling init_and_set_log_file_name() when opening binary log. - Remove newlines early when reading from index file. - Ensure that reset_logs() will work even if thd is 0 (Can happen on startup) - Added thd to sart_slave_threads() for better error handling.
* | Update sys_vars.sys_vars_wsrep result.Nirbhay Choubey2015-07-141-2/+2
| |
* | Merge branch '10.0-galera' into 10.1Nirbhay Choubey2015-07-14349-1095/+13714
| |
* | MDEV-8362 dash '-' is not recognized in charset armscii8 on select where queryAlexander Barkov2015-07-142-0/+40
| |
* | Cleanups, fixed warnings from valgrind, fixed failing tests (because on ↵Monty2015-07-107-12/+23
| | | | | | | | changes in WSREP initialization)
* | Fixed bug found by bar where we didn't properely check length of last ↵Monty2015-07-102-0/+27
| | | | | | | | | | | | | | | | argument for BETWEEN This should not have caused any notable errors in most cases. After fix, we are not using keys to solve MIN/MAX if the string used for comparision is longer thant the column-
* | Merge branch '10.1' of github.com:MariaDB/server into 10.1Monty2015-07-0968-65/+14054
|\ \ | | | | | | | | | | | | | | | | | | Conflicts: sql/item_subselect.cc Fixed also typo in comment
| * | MDEV-8336 The meaning of NO_ZERO_DATE is not clear for DATETIME.Alexander Barkov2015-07-082-0/+79
| | | | | | | | | | | | | | | | | | In some cases NO_ZERO_DATE did not allow datetime values with zero date part and non-zero time part (e.g. '0000-00-00 10:20:30.123456'). Allowing values of this kind in all known pieces of the code.
| * | MDEV-8419 utf32: compare broken bytes as "greater than any non-broken character"Alexander Barkov2015-07-072-0/+35
| | |
| * | Fix embedded result to reflect increased system variable's max value length.Nirbhay Choubey2015-07-061-14/+14
| | |
| * | Fixing a bug in MDEV-8418 (utf16, utf16le) and MDEV-8417 (utf8mb4).Alexander Barkov2015-07-068-132/+342
| | | | | | | | | | | | | | | Fixing non-BMP characters to have the same weight, as it was before MDEV-8418 and MDEV-8417.
| * | MDEV-8417 utf8mb4: compare broken bytes as "greater than any non-broken ↵Alexander Barkov2015-07-064-4/+183
| | | | | | | | | | | | character"
| * | MDEV-8415 utf8: compare broken bytes as "greater than any non-broken character"Alexander Barkov2015-07-031-3/+3
| | |
| * | MDEV-8215 Asian MB3 charsets: compare broken bytes as "greater than any ↵Alexander Barkov2015-07-034-0/+134
| | | | | | | | | | | | non-broken character"
| * | Tabular ANALYZE must get its data from execution trackerSergei Petrunia2015-07-022-1/+71
| | |
| * | Update test resultsSergei Petrunia2015-07-021-16/+22
| | |
| * | Adjust result files to reflect increased system variable's max value length.Nirbhay Choubey2015-07-013-23/+19
| | |
| * | Merge branch '10.1' of github.com:MariaDB/server into 10.1Sergei Petrunia2015-07-0110-0/+93
| |\ \
| | * | [MDEV-6877] Update test results to accound for binlog_row_image variable.Vicențiu Ciorbaru2015-07-011-0/+12
| | | | | | | | | | | | | | | | mysqld--help was not updated for binlog row image.
| | * | Checking in range_mrr_icp.result forgotten in the previous patch.Alexander Barkov2015-07-011-0/+24
| | | |
| | * | Add show warnings to test to find out the reason for create failure.Jan Lindström2015-07-018-0/+57
| | | |
| * | | MDEV-7811: EXPLAIN/ANALYZE FORMAT=JSON should show subquery cacheSergei Petrunia2015-07-011-122/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes over the original patch: - Fix variable/class/other names - Fix the JSON output to be in line with the output of other JSON constructs we produce
| * | | MDEV-7811: EXPLAIN/ANALYZE FORMAT=JSON should show subquery cacheOleksandr Byelkin2015-06-302-0/+244
| |/ /
| * | [MDEV-6877] Update test results to accound for binlog_row_image variable.Vicențiu Ciorbaru2015-06-302-0/+28
| | |
| * | [MDEV-6877] Added basic tests for binlog_row_image using minimal and noblob ↵Vicențiu Ciorbaru2015-06-308-0/+7374
| | | | | | | | | | | | values
| * | [MDEV-6877] Added tests for binlog_row_image using noblobs switchVicențiu Ciorbaru2015-06-306-0/+5069
| | |
| * | [MDEV-6877] Added test suite for binlog_row_image sys varVicențiu Ciorbaru2015-06-302-0/+229
| | |
| * | MDEV-8189 field<>const and const<>field are not symmetricAlexander Barkov2015-06-3012-0/+252
| | |
| * | Fix test failure where the environment was not fully restored.Jan Lindström2015-06-292-4/+4
| | |
* | | Fixes done while working on MDEV-4119:Monty2015-07-052-6/+112
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed several optimizer issues relatied to GROUP BY: a) Refering to a SELECT column in HAVING sometimes calculated it twice, which caused problems with non determinstic functions b) Removing duplicate fields and constants from GROUP BY was done too late for "using index for group by" optimization to work c) EXPLAIN SELECT ... GROUP BY did wrongly show 'Using filesort' in some cases involving "Using index for group-by" a) was fixed by: - Changed last argument to Item::split_sum_func2() from bool to int to allow more flags - Added flag argument to Item::split_sum_func() to allow on to specify if the item was in the SELECT part - Mark all split_sum_func() calls from SELECT with SPLIT_SUM_SELECT - Changed split_sum_func2() to do nothing if called with an argument that is not a sum function and doesn't include sum functions, if we are not an argument to SELECT. This ensures that in a case like select a*sum(b) as f1 from t1 where a=1 group by c having f1 <= 10; That 'a' in the SELECT part is stored as a reference in the temporary table togeher with sum(b) while the 'a' in having isn't (not needed as 'a' is already a reference to a column in the result) b) was fixed by: - Added an extra remove_const() pass for GROUP BY arguments before make_join_statistics() in case of one table SELECT. This allowes get_best_group_min_max() to optimize things better. c) was fixed by: - Added test for group by optimization in JOIN::exec_inner for select->quick->get_type() == QUICK_SELECT_I::QS_TYPE_GROUP_MIN_MAX item.cc: - Simplifed Item::split_sum_func2() - Split test to make them faster and easier to read - Changed last argument to Item::split_sum_func2() from bool to int to allow more flags - Added flag argument to Item::split_sum_func() to allow on to specify if the item was in the SELECT part - Changed split_sum_func2() to do nothing if called with an argument that is not a sum function and doesn't include sum functions, if we are not an argument to SELECT. opt_range.cc: - Simplified get_best_group_min_max() by calcuating first how many group_by elements. - Use join->group instead of join->group_list to test if group by, as join->group_list may be NULL if everything was optimized away. sql_select.cc: - Added an extra remove_const() pass for GROUP BY arguments before make_join_statistics() in case of one table SELECT. - Use group instead of group_list to test if group by, as group_list may be NULL if everything was optimized away. - Moved printing of "Error in remove_const" to remove_const() instead of having it in caller. - Simplified some if tests by re-ordering code. - update_depend_map_for_order() and remove_const() fixed to handle the case where make_join_statistics() has not yet been called (join->join_tab is 0 in this case)
* | MDEV-7792 - SQL Parsing Error - UNION AND ORDER BY WITH JOINSergey Vojtovich2015-06-292-0/+14
| | | | | | | | | | | | | | | | | | | | | | ORDER BY against union may confuse name resolution context, causing valid SQL statements to fail. The purpose of context change was presumably intended for the duration of gathering field list for ORDER BY. However it isn't actually required (name resolution context is never accessed by the latter). See also alternative solution (in MySQL 5.7): 92145b95.
* | MDEV-8391: encryption.innodb-page_encryption_compression failsJan Lindström2015-06-293-0/+36
| | | | | | | | | | | | Test create_or_replace should make sure that background decrypt operation is finished and flush all dirty pages using restart to clean up the database before ending.
* | update tests to passSergei Golubchik2015-06-282-2/+2
| |
* | bump the VERSION to 10.1.6 and related changesSergei Golubchik2015-06-288-17/+17
| | | | | | | | fix two #if MYSQL_VERSION_ID > 100105
* | Merge tag 'mariadb-10.0.20' into 10.1Sergei Golubchik2015-06-27129-189/+1768
|\ \
| * | MDEV-5309 - RENAME TABLE does not check for existence of the table's enginemariadb-10.0.20Sergei Golubchik2015-06-172-0/+5
| | | | | | | | | | | | fix the test case for ps-protocol
| * | MDEV-8287 DROP TABLE suppresses all engine errorsSergei Golubchik2015-06-166-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in ha_delete_table() * only convert ENOENT and HA_ERR_NO_SUCH_TABLE to warnings * only return real error codes (that is, not ENOENT and not HA_ERR_NO_SUCH_TABLE) * intercept HA_ERR_ROW_IS_REFERENCED to generate backward compatible ER_ROW_IS_REFERENCED in mysql_rm_table_no_locks() * no special code to handle HA_ERR_ROW_IS_REFERENCED * no special code to handle ENOENT and HA_ERR_NO_SUCH_TABLE * return multi-table error ER_BAD_TABLE_ERROR <table list> only when there were many errors, not when there were many tables to drop (but only one table generated an error)
| * | after-merge fixesSergei Golubchik2015-06-1610-37/+17
| | | | | | | | | | | | | | | in innobase: compilation error on windows other changes: perfschema merge followup
| * | Merge branch 'merge-perfschema-5.6' into 10.0Sergei Golubchik2015-06-1617-26/+16
| |\ \
| | * | 5.6.25Sergei Golubchik2015-06-1617-26/+16
| | | |
| * | | MDEV-5309 - RENAME TABLE does not check for existence of the table's engineSergey Vojtovich2015-06-162-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When RENAME TABLE is executed, it apparently does not check whether the engine is available (unlike ALTER TABLE .. RENAME, which does). It means that if the engine in question was not loaded on some reason, the table might become unusable, since the engine won't know about the change. With this patch RENAME TABLE fails if storage engine is not available.