- 05 Jun, 2014 1 commit
-
-
Alexander Barkov authored
"have_warnings" was set to an uninialized value when converting a negative number to datetime.
-
- 04 Jun, 2014 1 commit
-
-
Alexander Barkov authored
MDEV-6099 Bad results for DATE_ADD(.., INTERVAL 2000000000000000000.0 SECOND) MDEV-6097 Inconsistent results for CAST(int,decimal,double AS DATETIME) MDEV-6100 No warning on CAST(9000000 AS TIME)
-
- 02 Jun, 2014 3 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
unknown authored
mysql_derived_merge() made correctly working with views.
-
- 01 May, 2014 1 commit
-
-
unknown authored
It is triple bug with one test suite: 1. Incorrect outer table detection 2. Incorrect leaf table processing for multi-update (should be full like for usual updates and inserts) 3. ON condition fix_fields() fould be called for all tables of the query.
-
- 23 Apr, 2014 1 commit
-
-
Alexander Barkov authored
-
- 22 Apr, 2014 1 commit
-
-
Elena Stepanova authored
MariaDB-specific result replacement
-
- 21 Apr, 2014 4 commits
-
-
Elena Stepanova authored
A typo in include file caused the timeout counter to be 10x less than expected. It was fixed in 5.5.20+ along with a bigger change, now also fixing in 5.1-5.3.
-
Alexander Barkov authored
-
Alexander Barkov authored
MDEV-6134 SUBSTRING_INDEX returns wrong result for 8bit character sets when delimiter is not found Recording the forgotten test results.
-
Alexander Barkov authored
-
- 18 Apr, 2014 1 commit
-
-
Alexander Barkov authored
-
- 17 Apr, 2014 1 commit
-
-
Igor Babaev authored
Both bugs are caused by the same problem: the function optimize_cond() should update the value of *cond_equal rather than the value of join->cond_equal, because it is called not only for the WHERE condition, but for the HAVING condition as well.
-
- 11 Apr, 2014 3 commits
- 23 Mar, 2014 1 commit
-
-
Alexander Barkov authored
MDEV-5783 Assertion `0' failed in make_sortkey(SORTPARAM*, uchar*, uchar*) on ORDER BY HEX( UNCOMPRESSED_LENGTH( pk ) )
-
- 21 Mar, 2014 1 commit
-
-
unknown authored
-
- 18 Mar, 2014 1 commit
-
-
Sergey Petrunya authored
-
- 16 Mar, 2014 3 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 15 Mar, 2014 1 commit
-
-
Sergei Golubchik authored
-
- 14 Mar, 2014 1 commit
-
-
unknown authored
MDEV-5446: Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' fails on EXPLAIN EXTENDED with VALUES function field_index should be set correctly for null field created by Item_insert_value::fix_fields().
-
- 13 Mar, 2014 5 commits
-
-
Sergei Golubchik authored
(as it's done in 10.0)
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergey Petrunya authored
- With big_tables=ON, materialized table will use Aria (or MyISAM) SE, which allows prefix key reads. However, the temp.table has rec_per_key=NULL which causes the optimizer to crash when attempting to read index statistics for a prefix index read. - Fixed by providing a rec_per_key array with zeros (i.e. "no statistics data")
-
- 12 Mar, 2014 4 commits
- 07 Mar, 2014 1 commit
-
-
unknown authored
MDEV-5740: Assertion `!derived->first_select()->exclude_from_table_unique_test || derived->outer_select()-> exclude_from_table_unique_test' failed on 2nd execution of PS with derived_merge Do not check tables of executed units. Debug info about stages of derived tables execution added.
-
- 06 Mar, 2014 1 commit
-
-
Igor Babaev authored
The calls of the function remove_eq_conds() may change the and/or structure of the where conditions. So JOIN::equal_cond should be updated for non-recursive calls of remove_eq_conds().
-
- 21 Feb, 2014 1 commit
-
-
Igor Babaev authored
update_used_tables for the the where condition to update cached indicators of constant subexpressions. It should be done before further possible simplification of the where condition. This change caused simplification of the executed where conditions in many test cases.
-
- 19 Feb, 2014 3 commits
-
-
Sergey Petrunya authored
MDEV-4556 Server crashes in SEL_ARG::rb_insert with index_merge+index_merge_sort_union, FORCE INDEX - merge_same_index_scans() may put the same SEL_ARG tree in multiple result plans. make it call incr_refs() on the SEL_ARG trees that it does key_or() on, because key_or(sel_arg_tree_1, sel_arg_tree_2) call may invalidate SEL_ARG trees pointed by sel_arg_tree_1 and sel_arg_tree_2.
-
Sergey Petrunya authored
In function ‘void* memset(void*, int, size_t)’, inlined from ‘void Lifo_buffer::set_buffer_space(uchar*, uchar*)’ at sql_lifo_buffer.h:70:5, inlined from ‘int DsMrr_impl::dsmrr_init(handler*, RANGE_SEQ_IF*, void*, uint, uint, HANDLER_BUFFER*)’ at multi_range_read.cc:895:62: /usr/include/i386-linux-gnu/bits/string3.h:82:32: error: call to ‘__warn_memset_zero_len’ declared with attribute warning: memset used with constant zero length parameter; this could be due to transposed parameters [-Werror] It was intentional that the buffer is set to zero length there.
-
Sergey Petrunya authored
(gdb) p dbug_print_table_row(table) $33 = "SUBQUERY2_t1(col_int_key,col_varchar_nokey)=(7,c)"
-