summaryrefslogtreecommitdiff
path: root/mysql-test/main
Commit message (Collapse)AuthorAgeFilesLines
* dirty mergeOleksandr Byelkin2019-02-0727-28/+470
|
* Merge 10.2 into 10.3Marko Mäkelä2019-02-042-0/+16
|
* MDEV-18281 COM_RESET_CONNECTION changes the connection encodingVladislav Vaintroub2019-02-022-0/+35
| | | | | Store original charset during client authentication, and restore it for COM_RESET_CONNECTION
* Merge branch '10.2' into 10.3Sergei Golubchik2019-01-258-160/+189
|
* Merge 10.2 into 10.3Marko Mäkelä2019-01-249-18/+98
|
* MDEV-18152 Assertion 'num_fts_index <= 1' failedMarko Mäkelä2019-01-182-2/+4
| | | | | | | | | | | | | | | | | InnoDB does not allow creating multiple FULLTEXT INDEX in ALGORITHM=INPLACE. This constraint was not being properly enforced after MariaDB started to support ALGORITHM=INSTANT and instant ADD COLUMN. As a side effect of this bug, we again allow ALGORITHM=INPLACE to rebuild a table when one FULLTEXT INDEX survives. Also, we are returning a more accurate reason for refusing LOCK=NONE. innobase_fulltext_exist(): Return the number of fulltext indexes. ha_innobase::check_if_supported_inplace_alter(): If the table needs to be rebuilt, refuse the operation if multiple fulltext indexes would remain.
* Merge 10.2 into 10.3Marko Mäkelä2019-01-174-4/+77
|
* MDEV-18150 Assertion `decimals_to_set <= 38' failed in ↵Alexander Barkov2019-01-102-0/+15
| | | | Item_func_round::fix_length_and_dec_decimal
* Fix the location of test filesElena Stepanova2019-01-042-0/+139
|
* Merge branch '10.2' into 10.3Sergei Golubchik2019-01-0323-13/+302
|
* MDEV-17759 Assertion `precision > 0' failed in decimal_bin_size upon CREATE ↵Alexander Barkov2018-12-264-0/+92
| | | | TABLE .. SELECT
* MDEV-16036: Debug assertion failed in resignal on create temporary tableOleksandr Byelkin2018-12-202-0/+69
| | | | Reising condition on NOTW controlled by OPTION_SQL_NOTES.
* Merge 10.2 into 10.3Marko Mäkelä2018-12-1863-1219/+1244
|
* Merge 10.2 into 10.3Marko Mäkelä2018-12-122-0/+162
|
* MDEV-17967 Add a solution of the 8 queens problem to the regression test for CTESergei Golubchik2018-12-122-0/+72
|
* MDEV-17778: Alter table leads to a truncation warning with ANALYZE commandVarun Gupta2018-12-104-11/+40
| | | | | | Alter statement changed the THD structure by setting the value to FIELD_CHECK_WARN and then not resetting it back. This led ANALYZE to throw a warning which previously it didn't.
* Merge 10.2 into 10.3Marko Mäkelä2018-12-074-5/+57
|
* Merge 10.2 into 10.3Marko Mäkelä2018-12-042-0/+87
|
* Check that default() do not see invisible field.Oleksandr Byelkin2018-11-202-0/+4
|
* Merge 10.2 into 10.3Marko Mäkelä2018-11-201-0/+4
|
* Merge 10.2 into 10.3Marko Mäkelä2018-11-1919-9/+597
|
* MDEV-17278 CURSOR FOR LOOP - ERROR: unexpected end of stream, read 0 bytes ↵Alexander Barkov2018-11-142-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | (SERVER CRASH) sp_instr_cursor_copy_struct::exec_core() created TYPELIBs on a wrong mem_root, the one which is initialized in sp_head::execute(), this code: /* init per-instruction memroot */ init_sql_alloc(&execute_mem_root, "per_instruction_memroot", MEM_ROOT_BLOCK_SIZE, 0, MYF(0)); This memory root cleans up after every sp_instr_xxx executed, so later sp_instr_cfetch::execute() tried to use already freed and trashed memory. Changing sp_instr_cursor_copy_struct::exec_core() to call tmp.export_structure() inside this block (not outside of it): thd->set_n_backup_active_arena(thd->spcont->callers_arena, &current_arena); ... thd->restore_active_arena(thd->spcont->callers_arena, &current_arena); So now TYPELIBs created by sp_instr_cursor_copy_struct::exec_core() are still available and valid when sp_instr_cfetch::execute() is called. They are freed at the end of dispatch_command() corresponding to the "CALL p1" statement.
* MDEV-17253 Oracle compatibility: The REVERSE key word for FOR loop behaves ↵Alexander Barkov2018-11-133-8/+8
| | | | incorrectly
* MDEV-16241 Assertion `inited==RND' failed in handler::ha_rnd_end()Aleksey Midenkov2018-11-132-0/+21
| | | | | | | Discrepancy in open indexes due to overwritten `read_partitions` upon `ha_open()` in `ha_partition::clone()`. [Fixes tempesta-tech/mariadb#551]
* MDEV-17693 Shift/reduce conflicts for NAMES,ROLE,PASSWORD in the ↵Alexander Barkov2018-11-132-0/+139
| | | | option_value_no_option_type grammar
* Merge 10.2 into 10.3Marko Mäkelä2018-11-082-0/+214
|
* Merge 10.2 into 10.3Marko Mäkelä2018-11-072-0/+27
|
* MDEV-16697: Fix difference between 32bit/windows and 64bit systems in ↵Oleksandr Byelkin2018-11-072-0/+38
| | | | allowed select nest level
* MDEV-14429 sql_safe_updates in my.cnf not workSergei Golubchik2018-11-063-0/+8
| | | | add a test case
* MDEV-14429 sql_safe_updates in my.cnf not workVladislav Vaintroub2018-11-061-0/+5
|
* Merge 10.2 into 10.3Marko Mäkelä2018-11-0643-5463/+6110
| | | | | | | | | main.derived_cond_pushdown: Move all 10.3 tests to the end, trim trailing white space, and add an "End of 10.3 tests" marker. Add --sorted_result to tests where the ordering is not deterministic. main.win_percentile: Add --sorted_result to tests where the ordering is no longer deterministic.
* MDEV-17518: Range optimization doesn't use ON expressions from nested outer ↵Sergei Petrunia2018-11-053-0/+47
| | | | | | | joins Part#2: take into account that join nest that we are marking as constant might already have constant tables in it. Don't count these tables twice.
* MDEV-17518: Range optimization doesn't use ON expressions from nested outer ↵Sergei Petrunia2018-11-051-0/+32
| | | | | | joins Update .result files after the previous patch
* MDEV-17518: Range optimization doesn't use ON expressions from nested outer ↵Sergei Petrunia2018-11-052-0/+55
| | | | | | | joins Continuation of the fix: Make condition selectivity estimate use the right estimate, too.
* MDEV-17493: Partition pruning doesn't work for nested outer joinsSergei Petrunia2018-11-052-0/+64
| | | | Reuse the fix for MDEV-17518 here, too.
* MDEV-17518: Range optimization doesn't use ON expressions from nested outer ↵Sergei Petrunia2018-11-054-1/+63
| | | | joins
* MDEV-17359 Concatenation operator || in like expressionhalfspawn2018-10-182-0/+167
|
* Merge 10.2 into 10.3Marko Mäkelä2018-10-176-0/+241
|
* MDEV-17419 Subquery with group by returns wrong resultsIgor Babaev2018-10-172-0/+81
| | | | Added only test case because the bug was fixed by the patch for mdev-17382.
* MDEV-17137: Syntax errors with VIEW using MEDIANVarun Gupta2018-10-162-0/+30
| | | | | | | The syntax error happened because we had not implemented a different print for percentile functions. The syntax is a bit different when we use percentile functions as window functions in comparision to normal window functions. Implemented a seperate print function for percentile functions
* MDEV-17222 Reproducible server crash in String_list::append_str orIgor Babaev2018-10-142-19/+88
| | | | | | | | | | | | | | | in Field_iterator_table::create_item When IN predicate is converted to IN subquery we have to ensure that any item from the select list of the subquery has some name and this name is unique across the select list. This was not guaranteed by the code before the patch for MDEV-17222. If the name of an item of the select list was not set, and this happened for binary constants, then the server crashed. If the first row in the IN list contained the same constant in two different positions then the server returned an error message. This was fixed by providing all constants in the first row of the IN list with generated names.
* Adjusting old tests and adding new tests for "MDEV-8765: mysqldump -use ↵Alexander Barkov2018-10-128-46/+188
| | | | utf8mb4 by default"
* MDEV-17411 Wrong WHERE optimization with simple CASE and searched CASEAlexander Barkov2018-10-112-0/+49
|
* MDEV-17381 Wrong query result with LATERAL DERIVED optimizationIgor Babaev2018-10-082-0/+82
| | | | | | and join_cache_level=6 This bug was fixed by the patch for mdev-17382 applied to 5.5.
* MDEV-17382 Hash join algorithm should not be used to join materializedIgor Babaev2018-10-083-2/+81
| | | | | | | | | | | | | | | | | | | derived table / view by equality Now rows of a materialized derived table are always put into a temporary table before join operation. If BNLH is used to join this table with the result of a partial join then both operands of the join are actually put into main memory. In most cases this is not efficient. We could avoid this by sending the rows of the derived table directly to the join operation. However this kind of data flow is not supported yet. Fixed by not allowing usage of hash join algorithm to join a materialized derived table if it's joined by an equality predicate of the form f=e where f is a field of the derived table. Change for the test case in 10.3: splitting must be turned off to preserve the explain.
* MDEV-17167 - InnoDB: Failing assertion: table->get_ref_count() == 0 uponmariadb-10.3.10Sergey Vojtovich2018-10-022-0/+50
| | | | | | | | | | truncating a temporary table TRUNCATE expects only one TABLE instance (which is used by TRUNCATE itself) to be open. However this requirement wasn't enforced after "MDEV-5535: Cannot reopen temporary table". Fixed by closing unused table instances before performing TRUNCATE.
* Merge branch '10.2' into 10.3Sergei Golubchik2018-09-2838-155/+1343
|
* MDEV-16429: Assertion `!table || (!table->read_set || ↵Nikita Malyavin2018-09-212-0/+27
| | | | | | | | | | | | | | | bitmap_is_set(table->read_set, field_index))' fails upon attempt to update virtual column on partitioned versioned table When using buffered sort in `UPDATE`, keyread is used. In this case, `TABLE::update_virtual_field` should be aborted, but it actually isn't, because it is called not with a top-level handler, but with the one that is actually going to access the disk. Here the problemm is issued with partitioning, so the solution is to recursively mark for keyread all the underlying partition handlers. * ha_partition: update keyread state for child partitions Closes #800
* MDEV-17211 Server crash on queryIgor Babaev2018-09-172-0/+63
| | | | | | | The function JOIN_TAB::choose_best_splitting() did not take into account that for some tables whose fields were used in the GROUP BY list of the specification of a splittable materialized derived there might exist no elements in the array ext_keyuses_for_splitting.
* MDEV-16917 Index affects query resultsIgor Babaev2018-09-152-0/+52
| | | | | | | | | | | | The optimizer erroneously allowed to use join cache when joining a splittable materialized table together with splitting optimization. As a consequence in some rare cases the server returned wrong result sets for queries with materialized derived. This patch allows to use either join cache without usage of splitting technique for materialization of a splittable derived table or splitting without usage of join cache when joining such table. The costs the these alternatives are compared and the best variant is chosen.
View Lorry Controller Status