- 21 Apr, 2006 15 commits
-
-
unknown authored
into mysql.com:/M50/mysql-5.0
-
unknown authored
Make InnoDB option "loose", as the server might be started with this option just to find out the test is to be skipped in the configuration (bug#17359) mysql-test/t/innodb_unsafe_binlog-master.opt: Make InnoDB option "loose", as the server might be started with this option just to find out the test is to be skipped in the configuration (bug#17359)
-
unknown authored
client/mysql.cc: Auto merged
-
unknown authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
unknown authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
unknown authored
-
unknown authored
into mysql.com:/M50/mysql-5.0
-
unknown authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0 mysql-test/mysql-test-run.sh: Auto merged
-
unknown authored
-
unknown authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
unknown authored
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/my50-bug19190
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0 mysql-test/r/order_by.result: Auto merged sql/sql_select.cc: Auto merged sql/sql_yacc.yy: Auto merged mysql-test/t/func_gconcat.test: Manual merge mysql-test/t/order_by.test: Manual merge sql/sql_lex.h: Manual merge sql/sql_parse.cc: Manual merge sql/sql_union.cc: Manual merge
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
unknown authored
The bug caused wrong result sets for union constructs of the form (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2. For such queries order lists were concatenated and limit clause was completely neglected. mysql-test/r/order_by.result: Added a test case for bug #18767. mysql-test/t/order_by.test: Added a test case for bug #18767. sql/sql_lex.h: Fixed bug #18767. Placed the code the created a fake SELECT_LEX into a separate function. sql/sql_parse.cc: Fixed bug #18767. Placed the code the created a fake SELECT_LEX into a separate function. sql/sql_select.cc: Fixed bug #18767. Changed the condition on which a SELECT is treated as part of a UNION. The SELECT in (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2 now is handled in the same way as the first SELECT in a UNION sequence. sql/sql_union.cc: Fixed bug #18767. Changed the condition at which a SELECT is treated as part of a UNION. The SELECT in (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2 now is handled in the same way as the first SELECT in a UNION sequence. sql/sql_yacc.yy: Fixed bug #18767. Changed the condition at which a SELECT is treated as part of a UNION. The SELECT in (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2 now is handled in the same way as the first SELECT in a UNION sequence. In the same way is handled the SELECT in (SELECT ... LIMIT n) ORDER BY order list. Yet if there is neither ORDER BY nor LIMIT in the single-select union construct (SELECT ...) ORDER BY order_list then it is still handled as simple select with an order clause.
-
- 20 Apr, 2006 12 commits
-
-
unknown authored
Fixes for Bug#12429: Replication tests fail: "Slave_IO_Running" (?) differs related to MySQL 4.1 and Bug#16920 rpl_deadlock_innodb fails in show slave status (reported for MySQL 5.1) mysql-test/r/rpl_deadlock.result: Updated result
-
unknown authored
into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-1
-
unknown authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
unknown authored
into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-1
-
unknown authored
-
unknown authored
Remove duplicate test case for bug#14169 mysql-test/t/func_gconcat.test: Remove duplicate test case for bug#14169 mysql-test/r/func_gconcat.result: Remove duplicate test case for bug#14169
-
unknown authored
into production.mysql.com:/usersnfs/mleich/src
-
unknown authored
Clean up test case for bug#14169 mysql-test/t/func_gconcat.test: Clean up test case for bug#14169
-
unknown authored
into mysql.com:/M50/mysql-5.0
-
unknown authored
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0 mysys/mf_keycache.c: Auto merged ndb/src/kernel/SimBlockList.cpp: Auto merged ndb/src/kernel/blocks/ndbcntr/NdbcntrInit.cpp: Auto merged mysql-test/r/func_gconcat.result: Manual merge mysql-test/r/key_cache.result: Manual merge mysql-test/t/func_gconcat.test: Manual merge mysql-test/t/key_cache.test: Manual merge sql/item_func.cc: Manual merge sql/item_sum.h: Manual merge sql/lock.cc: Manual merge sql/sql_select.cc: Manual merge sql/unireg.h: Manual merge
-
- 19 Apr, 2006 9 commits
-
-
unknown authored
Temporarily commented out a query from the test case for bug 14169 to make it pass with --ps-protocol. mysql-test/r/func_gconcat.result: Added DROP TABLE command to the test case for bug 14169.
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-2
-
unknown authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
unknown authored
into moonbone.local:/work/14169-bug-4.1-mysql
-
unknown authored
Corrected test case for the bug#14169 to make it pass in --ps-protocol mode. mysql-test/r/func_gconcat.result: Corrected test case for the bug#14169 to make it pass in --ps-protocol mode.
-
unknown authored
After a locking error the open table(s) were not fully cleaned up for reuse. But they were put into the open table cache even before the lock was tried. The next statement reused the table(s) with a wrong lock type set up. This tricked MyISAM into believing that it don't need to update the table statistics. Hence CHECK TABLE reported a mismatch of record count and table size. Fortunately nothing worse has been detected yet. The effect of the test case was that the insert worked on a read locked table. (!) I added a new function that clears the lock type from all tables that were prepared for a lock. I call this function when a lock failes. No test case. One test would add 50 seconds to the test suite. Another test requires file mode modifications. I added a test script to the bug report. It contains three cases for failing locks. All could reproduce a table corruption. All are fixed by this patch. This bug was not lock timeout specific. sql/lock.cc: Bug#18544 - LOCK TABLES timeout causes MyISAM table corruption Resetting the lock type in the open table(s) lock data after a locking error.
-
unknown authored
mysql-test/mysql-test-run.sh: Use 'test', not '[' as the shell builtin might not have '-L
-
unknown authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/merge ndb/src/mgmclient/CommandInterpreter.cpp: Auto merged
-
unknown authored
The bug caused a reported index corruption in the cases when key_cache_block_size was not a multiple of myisam_block_size, e.g. when key_cache_block_size=1536 while myisam_block_size=1024. mysql-test/r/key_cache.result: Added a test case for bug #19079. mysql-test/t/key_cache.test: Added a test case for bug #19079.
-
- 18 Apr, 2006 4 commits
-
-
unknown authored
into mysql.com:/home/matthias/Arbeit/mysql-4.1/src-1
-
unknown authored
into mysql.com:/home/matthias/Arbeit/mysql-5.0/src-1
-
unknown authored
Stepped up version to 5.0.20a configure.in: Stepped up version to 5.0.20a
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-release
-