- 26 Mar, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
- 19 Mar, 2008 2 commits
-
-
cmiller@zippy.cornsilk.net authored
-
cmiller@zippy.cornsilk.net authored
isn't running Pass the process id of the manager as a parameter to "wait_for_pid" and if the manager isn't running, then do not continue to wait. Also, capture the error message of our process-existence test, "kill -0", as we expect errors and shouldn't pass them to the user. Additionally, be a bit more descriptive of what the problem is.
-
- 13 Mar, 2008 3 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-build
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug34192/my51-bug34192
-
- 12 Mar, 2008 7 commits
-
-
cmiller@zippy.cornsilk.net authored
databases from 4.0 server mysqldump treated a failure to set the results charset as a severe error. Now, don't try to set the charset for the SHOW CREATE TABLE statement, if remote server's version is earlier than 4.1, which means it doesn't support changing charsets.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
cmiller@zippy.cornsilk.net authored
table with backticks (Thanks to Lu Jingdong, though I did not take his patch directly, as it contained a significant flaw.) It wasn't a backtick/parsing problem. We merely didn't anticipate and allocate enough space to handle the optional "#mysql50#" table- name prefix. Now, allocate that extra space in case we need it when we look up a legacy table to get its file's name.
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.1-build-src-clean
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.1-build-src-clean
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.0-build-src-clean
-
mleich@five.local.lan authored
ChangeSet@1.2565, 2008-03-11 20:20:49+01:00 Merge five.local.lan:/work/merge/mysql-5.0-funcs_1 into five.local.lan:/work/merge/mysql-5.1-funcs_1 MERGE: 1.1810.3473.26 ChangeSet@1.1810.3473.26, 2008-03-11 19:54:35+01:00 Post fix for WL#4203 Reorganize and fix the data dictionary tests of testsuite funcs_1 The final fix of Bug#34532 Some funcs_1 tests do not clean up at end of testing and some minor additional modifications are for happens here
-
- 11 Mar, 2008 7 commits
-
-
mleich@five.local.lan authored
into five.local.lan:/work/merge/mysql-5.1-funcs_1
-
mleich@five.local.lan authored
WL#4203 Reorganize and fix the data dictionary tests of testsuite funcs_1 because the goal to fix Bug#34532 Some funcs_1 tests do not clean up at end of testing was partially missed. Some minor additional modifications are for WL#4304 Cleanup in funcs_1 tests
-
joerg@trift2. authored
into trift2.:/MySQL/M51/win-scripts-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M51/win-scripts-5.1
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/build/mysql-5.1-build
-
kent@mysql.com/kent-amd64.(none) authored
Include .pdb files for tools and libraries (bug#35104)
-
joerg@trift2. authored
into trift2.:/MySQL/M50/win-scripts-5.0
-
- 10 Mar, 2008 3 commits
-
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.1-build-src-clean
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.1-build-src-clean
-
mleich@five.local.lan authored
into five.local.lan:/work/trees/mysql-5.0-build-src-clean
-
- 07 Mar, 2008 6 commits
-
-
iggy@amd64.(none) authored
into amd64.(none):/src/bug27101/my51-bug27101
-
iggy@amd64.(none) authored
into amd64.(none):/src/bug27101/my51-bug27101
-
iggy@amd64.(none) authored
- Make sure mysqlhotcopy doesn't create unrestorable slaves.
-
mleich@five.local.lan authored
ChangeSet@1.2561, 2008-03-07 17:44:03+01:00, mleich@five.local.lan +132 -0 Merge five.local.lan:/work/merge/mysql-5.0-funcs_1 into five.local.lan:/work/merge/mysql-5.1-funcs_1 MERGE: 1.1810.3473.24 ChangeSet@1.1810.3473.24, 2008-03-07 WL#4203 Reorganize and fix the data dictionary tests of testsuite funcs_1 1. Adjustment of expected results to modified server properties 2. Add some tests of information_schema views 3. Minor corrections and improvements
-
mleich@five.local.lan authored
into five.local.lan:/work/merge/mysql-5.1-funcs_1
-
mleich@five.local.lan authored
testsuite funcs_1 1. Fix the following bugs Bug#30440 "datadict" tests (all engines) fail: Character sets depend on configuration Solution: Test variants charset_collation_* adjusted to different builds Bug#32603 "datadict" tests (all engines) fail in "community" tree: "PROFILING" table Solution: Excluding "PROFILING" table from queries Bug#33654 "slow log" is missing a line Solution: Unify the content of the fields TABLES.TABLE_ROWS and STATISTICS.CARDINALITY within result sets Bug#34532 Some funcs_1 tests do not clean up at end of testing Solution: DROP objects/reset global server variables modified during testing + let tests missing implementation end before loading of tables Bug#31421 funcs_1: ndb__datadict fails, discrepancy between scripts and expected results Solution: Cut <engine>__datadict tests into smaller tests + generate new results. Bug#33599 INFORMATION_SCHEMA.STATISTICS got a new column INDEX_COMMENT: tests fail (2) Generation of new results during post merge fix Bug#33600 CHARACTER_OCTET_LENGTH is now CHARACTER_MAXIMUM_LENGTH * 4 Generation of new results during post merge fix Bug#33631 Platform-specific replace of CHARACTER_MAXIMUM_LENGTH broken by 4-byte encoding Generation of new results during post merge fix + removal of platform-specific replace routine (no more needed) 2. Restructure the tests - Test not more than one INFORMATION_SCHEMA view per testscript - Separate tests of I_S view layout+functionality from content related to the all time existing databases "information_schema", "mysql" and "test" - Avoid storage engine related variants of tests which are not sensible to storage engines at all. 3. Reimplement or add some subtests + cleanup There is a some probability that even the reviewed changeset - does not fix all bugs from above or - contains new bugs which show up on some platforms <> Linux or on one of the various build types 4. The changeset contains fixes according to - one code review - minor bugs within testing code found after code review (accepted by reviewer) - problems found during tests with 5.0.56 in build environment
-
- 06 Mar, 2008 4 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
cmiller@zippy.cornsilk.net authored
field names Add a test that proves the bug is fixed. This doesn't add any new server code.
-
into chorlton.adsl.perkin.org.uk:/Users/jonathan/mysql/bk/build/5.1
-
into chorlton.adsl.perkin.org.uk:/Users/jonathan/mysql/bk/bug-31736/5.1
-
- 05 Mar, 2008 7 commits
-
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
cmiller@zippy.cornsilk.net authored
grant warnings on embedded server.
-
cmiller@zippy.cornsilk.net authored
The DBUG code emits the current value of the proc_info member of THD, which may be set to NULL. It was wrong to dereference that value with the format string %s without verifying that it was valid. Now, insert an inline test that substitutes the string "(null)" for NULL pointers.
-
cmiller@zippy.cornsilk.net authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.1-build
-
cmiller@zippy.cornsilk.net authored
The cause of the crash is an assertion failure that we do not emit an error message (grant not found) and then return "ok". The assertion is valid, and we were ignoring the buggy behavior prior to the "Diagnostics" result-verification. Use an error handler to mutate innocuous missing-grant errors, when removing routines, into warnings.
-
joerg@trift2. authored
-