- 09 Apr, 2006 2 commits
- 08 Apr, 2006 1 commit
-
-
unknown authored
Removing the problematic line from include test file. mysql-test/include/get_binlog_dump_thread_id.inc: replacing replace_result by disable_query_log mysql-test/r/rpl_temporary.result: results
-
- 07 Apr, 2006 17 commits
-
-
unknown authored
into dl145j.mysql.com:/tmp/5.0.21-bug17284-temp_table
-
unknown authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
unknown authored
into mysql.com:/M50/mtr-5.0
-
unknown authored
into mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.21-bug17284-temp_table
-
unknown authored
-
unknown authored
Idea of the fix is for master to send FD event with `created' as 0 to reconnecting slave (upon slave_net_timeout, no master crash) to avoid destroying temp tables. In a case of a connect by slave to the master after its crash temp tables have been already cleaned up so that slave can not keep `orphan' temp tables. mysql-test/r/rpl_temporary.result: results mysql-test/t/rpl_temporary.test: wait-free addon to check temp tables are ok after slave reconnect. sql/sql_repl.cc: Storing zero for assigning to `created' of FD event on the reconnecting slave. mysql-test/include/get_binlog_dump_thread_id.inc: mysqltest's preudo-macro to calculate $id master dump thread id
-
unknown authored
-
unknown authored
mysql-test/mysql-test-run.sh: Provide info about the options used for this run to any evaluation tool.
-
unknown authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
unknown authored
mysql-test/mysql-test-run.pl: Manual merge (no idea why automatic merge failed ...).
-
unknown authored
mysql-test/mysql-test-run.pl: Add option "with-ndbcluster-only" (ignored) for compatibility with newer "Do-compile".
-
unknown authored
mysql-test/lib/mtr_process.pl: Auto merged
-
unknown authored
mysql-test/lib/mtr_process.pl: Change from "mtr_error()" to "mtr_warning()" on some problems, because "error" makes the whole suite abort which then makes "Do-compile" terminate, so none of the following steps (including other etst suites) will be done.
-
unknown authored
mysql-test/mysql-test-run.sh: Manual merge from 4.0 (which was a 5.1 backport): "--with-ndbcluster" is already present, "--with-ndbcluster-only" is really usable here.
-
unknown authored
mysql-test/r/func_time.result: expected test results for bug #18100 added mysql-test/t/func_time.test: test case for bug #18100 added sql/item_timefunc.cc: wrong formula for EXTRACT QUARTER, now uses the same calculus as the QUARTER() function
-
unknown authored
skip charset aggregation for order columns
-
unknown authored
move test case for bug 14290 to ctype_ucs test
-
- 06 Apr, 2006 18 commits
-
-
unknown authored
The problem was due to the fact that with --lower-case-table-names set to 1 the function find_field_in_group did not convert the prefix 'HU' in HU.PROJ.CITY into lower case when looking for it in the group list. Yet the names in the group list were extended by the database name in lower case. mysql-test/r/having.result: Added a test case for bug #15917. mysql-test/t/having.test: Added a test case for bug #15917. sql/item.cc: Fixed bug #15917: unexpected complain for a NIST test case. The problem was due to the fact that with --lower-case-table-names set to 1 the function find_field_in_group did not convert the prefix 'HU' in HU.PROJ.CITY into lower case when looking for it in the group list. Yet the names in the group list were extended by the database name in lower case. The needed conversion was added to the code of find_field_in_group.
-
unknown authored
into mysql.com:/home/greenman/workspace-mysql/mysql/bug-5.0-16240
-
unknown authored
into mysql.com:/home/psergey/mysql-5.0-bug18237-review
-
unknown authored
-
unknown authored
support-files/mysql.server.sh: Fixed so that if the datadir has been set via the command line, it won't be reset by specifing the basedir after.
-
unknown authored
mysql-test/mysql-test-run.sh: Make "mysql-test-run.sh" accept (and ignore) the options "--with-ndbcluster" and "--with-ndbcluster-only". This is necessary because newer build tools will issue them, and the test script should tolerate that. Backport from 5.1 (Tomas Ulin, 2006-01-17)
-
unknown authored
into april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.0
-
unknown authored
counter". When TRUNCATE TABLE was called within an stored procedure the auto_increment counter was not reset to 0 even if straight TRUNCATE for this table did this. This fix makes TRUNCATE in stored procedures to be handled exactly in the same way as straight TRUNCATE. We achieve this by rolling back the fix for bug 8850, which is no longer needed since stored procedures don't require prelocked mode anymore (and TRUNCATE is not allowed in stored functions or triggers). mysql-test/r/sp.result: Test case for BUG#14945. mysql-test/t/sp.test: Test case for BUG#14945. sql/sql_delete.cc: Handle TRUNCATE in stored procedures exactly in the same way as straight TRUNCATE (i.e. without falling back to DELETE if possible). We achieve this by rolling back the fix for bug 8850, which is no longer relevant since stored procedures don't require prelocked mode anymore (and TRUNCATE is not allowed in stored functions or triggers). sql/sql_parse.cc: Handle TRUNCATE in stored procedures exactly in the same way as straight TRUNCATE (i.e. without falling back to DELETE if possible). We achieve this by rolling back the fix for bug 8850, which is no longer relevant since stored procedures don't require prelocked mode anymore (and TRUNCATE is not allowed in stored functions or triggers).
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
unknown authored
as it is now required by mysql_set_character_set() libmysql/libmysql.c: Removing mysql_get_server_version() sql-common/client.c: Adding mysql_get_server_version()
-
unknown authored
Bug#18830 incompatibility new libraries with old server Additional 5.0 fix: applying the same patch to client.c. sql-common/client.c: Bug#18830 incompatibility new libraries with old server Additional 5.0 fix: applying the same patch to client.c.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0 libmysql/libmysql.c: Bug#18830 incompatibility new libraries with old server Mergeing from 4.1
-
unknown authored
Bug#18830: incompatibility new libraries with old server Don't execute SET NAMES with pre-4.1 server. libmysql/libmysql.c: Bug#18830: incompatibility new libraries with old server Don't execute SET NAMES with pre-4.1 server.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0
-
unknown authored
Adding test case to cover queries which worked incorrectly earlier: Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci mysql-test/r/ctype_latin1.result: Adding test case for Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci mysql-test/t/ctype_latin1.test: Adding test case for Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci
-
unknown authored
Using local. strings/ctype-extra.c: Using local.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0 strings/conf_to_src.c: Auto merged
-
unknown authored
Backporting a 5.0 change: MAX_BUF was too small for Index.xml Changeing MAX_BUF and adding assert to easier catch the same problem in the future. ctype-extra.c: Regenerating ctype-extra.c with the fixed conf_to_src. strings/ctype-extra.c: Regenerating ctype-extra.c with the fixed conf_to_src. strings/conf_to_src.c: Backporting a 5.0 change: MAX_BUF was too small for Index.xml Changeing MAX_BUF and adding assert to easier catch the same problem in the future.
-
- 05 Apr, 2006 2 commits
-
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
unknown authored
Buffer was too small to load Index.xml. So some charsets were not gerenrated. Making the buffer bigger, and adding an DBUG_ASSERT, to easier catch the problem in the future. ctype-extra.c: Additional charsets were generated. strings/ctype-extra.c: Additional charsets were generated. strings/conf_to_src.c: Buffer was too small to load Index.xml. So some charsets were not gerenrated. Making the buffer bigger, and adding an DBUG_ASSERT, to easier catch the problem in the future.
-