- 01 May, 2008 3 commits
-
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam
-
tsmith@ramayana.hindu.god authored
(fix warnings).
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/51
-
- 30 Apr, 2008 11 commits
-
-
tsmith@ramayana.hindu.god authored
-
hhunger@hh-nb.hungers authored
into hh-nb.hungers:/work/merge/mysql-5.1-build
-
hhunger@hh-nb.hungers authored
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
davi@mysql.com/endora.local authored
The problem is that since MyISAM's concurrent_insert is on by default some concurrent SELECT statements might not see changes made by INSERT statements in other connections, even if the INSERT statement has returned. The solution is to disable concurrent_insert so that INSERT statements returns after the data is actually visible to other statements.
-
davi@endora.local authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
hhunger@hh-nb.hungers authored
into hh-nb.hungers:/work/merge/mysql-5.1-build
-
hhunger@hh-nb.hungers authored
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/51
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/51
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/bugteam/mrg/51
-
- 29 Apr, 2008 2 commits
-
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/bugteam/mrg/51
-
davi@mysql.com/endora.local authored
Enable back the disabled test case.
-
- 28 Apr, 2008 10 commits
-
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my51-rel_clean_up
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my50-rel_clean_up
-
iggy@amd64.(none) authored
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my51-rel_clean_up
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my51-rel_clean_up
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my50-rel_clean_up
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my51-rel_clean_up
-
iggy@amd64.(none) authored
into amd64.(none):/src/rel_clean_up/my50-rel_clean_up
-
iggy@amd64.(none) authored
-
gshchepa/uchum@host.loc authored
into host.loc:/work/bk/5.1-bugteam
-
- 26 Apr, 2008 1 commit
-
-
pcrews@pcrews-mac-local.local authored
Bug#36033 - Test funcs_1.processlist_val_ps fails on Windows Bug#36034 - Test parts.part_supported_sql_func_<eng> fails on Windows Bug#36036 - Test parts.partition_alter1_<eng> fails on Windows Bug#36037 - Test parts.partition_alter2_<eng> fails on Windows Bug#36038 - Test parts.partition_basic_<engine> failing on Windows Bug#36039 - Test parts.partition_engine_<eng> fails on Windows Bug#36040 - Test parts.partition_syntax_<eng> fails on Windows Changeset to fix multiple 5.1.24-rc build bugs on Windows platforms. Many of these bugs had the same root causes.
-
- 25 Apr, 2008 1 commit
-
-
gshchepa/uchum@host.loc authored
for ENGINE=MRG_MYISAM (should be optimized out). Before WL#3281 MERGE engine had the HA_NOT_EXACT_COUNT flag unset, and it worked with COUNT optimization as desired. After the removal of the HA_NOT_EXACT_COUNT flag neither HA_STATS_RECORDS_IS_EXACT (opposite to former HA_NOT_EXACT_COUNT flag) nor modern HA_HAS_RECORDS flag were not added to MERGE table flag mask. 1. The HA_HAS_RECORDS table flag has been set. 2. The ha_myisammrg::records method has been overridden to calculate total number of records in underlying tables.
-
- 24 Apr, 2008 4 commits
-
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.1-bug35844
-
evgen@moonbone.local authored
When a zero length is provided to the my_decimal_length_to_precision function along with unsigned_flag set to false it returns a negative value. For queries that employs temporary tables may cause failed assertion or excessive memory consumption while temporary table creation. Now the my_decimal_length_to_precision and the my_decimal_precision_to_length functions take unsigned_flag into account only if the length/precision argument is non-zero.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
and main: user_limits, concurrent_innodb, lowercase_table3, ctype_create tests.
-
- 23 Apr, 2008 6 commits
-
-
hhunger@hh-nb.hungers authored
into hh-nb.hungers:/work/merge/mysql-5.1-build
-
hhunger@hh-nb.hungers authored
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.1-bugteam
-
gshchepa/uchum@host.loc authored
Post-commit minor cleanup of testcase (bug#36139).
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.1-bugteam
-
igor@olga.mysql.com authored
The function test_if_skip_sort_order ignored any covering index used for ref access of a table in a query with ORDER BY if this index was incompatible with the ORDER BY list and there was another covering index compatible with this list. As a result sub-optimal execution plans were chosen for some queries with ORDER BY clause.
-
- 22 Apr, 2008 2 commits
-
-
gshchepa/uchum@host.loc authored
into host.loc:/home/uchum/work/5.0-bugteam
-
gshchepa/uchum@host.loc authored
impossible WHERE/HAVING clause (subselect_single_select_engine::exec). Allocation and initialization of joined table list t1, t2... of subqueries like: NOT IN (SELECT ... FROM t1,t2,... WHERE 0) is optimized out, however server tries to traverse this list.
-