- 29 Apr, 2011 8 commits
-
-
Bjorn Munch authored
-
Bjorn Munch authored
-
Bjorn Munch authored
-
Mattias Jonsson authored
-
Georgi Kodinov authored
Removed STDCALL from the function definition.
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-
- 28 Apr, 2011 2 commits
-
-
Georgi Kodinov authored
Enabled the ABI check to run on MacOSX.
-
Georgi Kodinov authored
-
- 27 Apr, 2011 9 commits
-
-
Mattias Jonsson authored
-
Mattias Jonsson authored
Partitions can have different ref_length (position data length). Removed DBUG_ASSERT which crashed debug builds when using MAX_ROWS on some partitions.
-
Sven Sandberg authored
-
Nirbhay Choubey authored
-
Nirbhay Choubey authored
FAILS WITH LIBEDIT Fixed by checking the return value of the write() function calls and handling the open files and fd appropriately. cmd-line-utils/libedit/vi.c: BUG#12329909 - BUILDING MYSQL WITH DEBUG SUPPORT FAILS WITH LIBEDIT Added a check on the return value of the write() function calls.
-
Magnus Blåudd authored
- fix the fix to properly detect when engine is NDB and also don't drop the table t9 if it hasn't been created
-
Sergey Glukhov authored
-
Bjorn Munch authored
Fix: it only worked if some worker had valgrind report from its last test Flag has to be set both places where report is printed
-
Sergey Glukhov authored
calc_daynr() function returns negative result if malformed date with zero year and month is used. Attempt to calculate week day on negative value leads to crash. The fix is return NULL for 'W', 'a', 'w' specifiers if zero year and month is used. Additional fix for calc_daynr(): --added assertion that result can not be negative --return 0 if zero year and month is used mysql-test/r/func_time.result: test case mysql-test/t/func_time.test: test case sql-common/my_time.c: --added assertion that result can not be negative --return 0 if zero year and month is used sql/item_timefunc.cc: eturn NULL for 'W', 'a', 'w' specifiers if zero year and month is used.
-
- 26 Apr, 2011 9 commits
-
-
Guilhem Bichot authored
-
Guilhem Bichot authored
-
Guilhem Bichot authored
-
Mattias Jonsson authored
-
Guilhem Bichot authored
-
Mattias Jonsson authored
-
Guilhem Bichot authored
-
Bjorn Munch authored
-
Mattias Jonsson authored
-
- 25 Apr, 2011 2 commits
-
-
Serge Kozlov authored
-
Serge Kozlov authored
-
- 23 Apr, 2011 3 commits
-
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-
Mattias Jonsson authored
-
- 22 Apr, 2011 3 commits
-
-
Sergey Glukhov authored
-
Sergey Glukhov authored
Before sorting HAVING condition is split into two parts, first part is a table related condition and the rest of is HAVING part. Extraction of HAVING part does not take into account the fact that some of conditions might be non-const but have 'used_tables' == 0 (independent subqueries) and because of that these conditions are cut off by make_cond_for_table() function. The fix is to use (table_map) 0 instead of used_tables in third argument for make_cond_for_table() function. It allows to extract elements which belong to sorted table and in addition elements which are independend subqueries. mysql-test/r/having.result: test case mysql-test/t/having.test: test case sql/sql_select.cc: The fix is to use (table_map) 0 instead of used_tables in third argument for make_cond_for_table() function. It allows to extract elements which belong to sorted table and in addition elements which are independend subqueries.
-
Sergey Vojtovich authored
-
- 21 Apr, 2011 4 commits
-
-
Vasil Dimov authored
-
Vasil Dimov authored
-
Vasil Dimov authored
-
Vasil Dimov authored
-