- 05 May, 2008 1 commit
-
-
unknown authored
into mysql1000.dsl.inet.fi:/home/andrei/MySQL/BARE/mysql-5.1-bugteam
-
- 02 May, 2008 6 commits
-
-
unknown authored
-
unknown authored
into pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-bugteam client/mysqltest.c: Auto merged dbug/dbug.c: Auto merged mysql-test/mysql-test-run.pl: Auto merged client/mysql_upgrade.c: SCCS merged
-
unknown authored
client/mysql_upgrade.c: Add --tmpdir option to mysql_upgrade and use it when creating temporary files. mysql-test/mysql-test-run.pl: Pass --tmpdir to mysql_upgrade
-
unknown authored
- Code in DbugParse was reading from beyond end of the control string dbug/dbug.c: Don't try to parse control strings that hasn't got any tokens or is zero size
-
unknown authored
client/mysqltest.c: Use the --tmpdir location to create temporary files
-
unknown authored
mysql-test/mysql-test-run.pl: Use the requested tmpdir in 'collect_mysqld_features', create it if it does not already exists
-
- 01 May, 2008 15 commits
-
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.0-trigs
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs client/mysqltest.c: Auto merged
-
unknown authored
into pcrews-mac-local.local:/Users/pcrews/usr/local/bin/data0/build_work/mysql-5.1-trigs client/mysqltest.c: Auto merged
-
unknown authored
Bug#36028 - Test funcs_1.<engine>_trig_03e failing on Windows Bug#36029 - Test funcs_1.<engine>_trig_0407 failing on Windows Bug#36030 - Test funcs_1.<engine>_trig_08 failing on Windows Adding $MASTER_MYSOCK to init_win_path() When path names are short, master.sock ends up in MYSQL_TMP_DIR, but with longer path names, master.sock ends up in /tmp/<random_string>/ and these tests will fail due to path delimiter difference. New changeset to start with 5.0 -- Not all of these tests are present in 5.0, but want to keep mysqltest the same
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/autopush/B36041-5.1-bugteam
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/autopush/B36041-5.1-bugteam
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/autopush/B35298-5.1-bugteam configure.in: Auto merged
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam configure.in: merge 5.0-bugteam to 5.1-bugteam
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/work/B35298-5.1-bugteam mysql-test/r/func_gconcat.result: Auto merged mysql-test/t/func_gconcat.test: Auto merged sql/item_sum.cc: Auto merged configure.in: merge 5.0-bugteam to 5.1-bugteam
-
unknown authored
The bug is a regression introduced by the patch for bug32798. The code in Item_func_group_concat::clear() relied on the 'distinct' variable to check if 'unique_filter' was initialized. That, however, is not always valid because Item_func_group_concat::setup() can do shortcuts in some cases w/o initializing 'unique_filter'. Fixed by checking the value of 'unique_filter' instead of 'distinct' before dereferencing. mysql-test/r/func_gconcat.result: Added test cases for bugs #35298 and #36024. mysql-test/t/func_gconcat.test: Added test cases for bugs #35298 and #36024. sql/item_sum.cc: Check if unique_filter != NULL before dereferencing it. Non-zero value of distinct does not always mean that unique_filter is initialized because Item_func_group_concat::setup() can do shortcuts is some cases
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam
-
unknown authored
into magare.gmz:/home/kgeorge/mysql/work/merge-5.1-bugteam mysql-test/t/disabled.def: Auto merged
-
unknown authored
(fix warnings). libmysqld/lib_sql.cc: Use ulonglong to store row count in Protocol_text::remove_last_row() (fix warnings).
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/51 mysql-test/t/disabled.def: manual merge
-
- 30 Apr, 2008 12 commits
-
-
unknown authored
mysql-test/r/group_concat_max_len_func.result: Properly restore global group_concat_max_len value at end of test mysql-test/t/disabled.def: Re-disable user_limits test; it is still failing randomly (bug 33696) mysql-test/t/group_concat_max_len_func.test: Update test results
-
unknown authored
Select of the test could not perform deterministically, because the table remains to be updatable by the running event handler. Fixed with changing verification to use a logical values instead of comparison with a pre-recorded results. mysql-test/include/rpl_events.inc: changing verification to use a logical values instead of comparison with a pre-recorded results mysql-test/suite/rpl/r/rpl_events.result: resutls updated.
-
unknown authored
into hh-nb.hungers:/work/merge/mysql-5.1-build mysql-test/t/disabled.def: Auto merged
-
unknown authored
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
unknown 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. mysql-test/r/client_xml.result: Update test case result. mysql-test/r/federated.result: Update test case result. mysql-test/r/federated_bug_25714.result: Update test case result. mysql-test/t/client_xml.test: Disable concurrent insert and restore old value at the end of the test so it doesn't affect other tests. mysql-test/t/federated.test: Disable concurrent insert and restore old value at the end of the test so it doesn't affect other tests. mysql-test/t/federated_bug_25714.test: Disable concurrent insert and restore old value at the end of the test so it doesn't affect other tests.
-
unknown authored
into mysql.com:/Users/davi/mysql/mysql-5.1-bugteam
-
unknown authored
into hh-nb.hungers:/work/merge/mysql-5.1-build BitKeeper/deleted/.del-myisam_use_mmap_basic.result: Delete: mysql-test/r/myisam_use_mmap_basic.result BitKeeper/deleted/.del-myisam_use_mmap_basic.test: Delete: mysql-test/t/myisam_use_mmap_basic.test
-
unknown authored
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/51 mysql-test/suite/rpl/r/rpl_packet.result: Auto merged mysql-test/suite/rpl/t/disabled.def: Auto merged mysql-test/suite/rpl/t/rpl_packet.test: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/build/51 mysql-test/mysql-test-run.pl: Auto merged mysql-test/suite/funcs_1/datadict/processlist_val.inc: Auto merged mysql-test/t/disabled.def: Auto merged mysql-test/suite/rpl/t/disabled.def: SCCS merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/bugteam/mrg/51
-
- 29 Apr, 2008 3 commits
-
-
unknown authored
100% effectively on Windows The mysqltest docs state that the 'replace_result' command doesn't perform any escape processing. However the current implementation was processing backslash escapes in the from/to strings. This prevents replacing e.g. patch on windows (where backslash is used as a path separator). Fixed by removing the backslash escape processing from 'replace_result'. client/mysqltest.c: Bug #36041: remove the escape processing from --replace_result mysql-test/r/mysqltest.result: Bug #36041: test case mysql-test/t/mysqltest.test: Bug #36041: test case
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/bugteam/mrg/51 mysql-test/suite/rpl/r/rpl_packet.result: Auto merged mysql-test/suite/rpl/t/rpl_packet.test: Auto merged mysql-test/suite/rpl/t/disabled.def: SCCS merged
-
unknown authored
Enable back the disabled test case. mysql-test/include/mix1.inc: Fix a race condition in the test, causing a sporadic failure. mysql-test/r/innodb_mysql.result: Update test case result. mysql-test/t/disabled.def: Enable the test case innodb_mysql. sql/sql_parse.cc: Fix the random failure of innodb_mysql test. The failure is not random any more after a patch for Bug 12713 added asserts around handler commit.
-
- 28 Apr, 2008 3 commits