- 05 Jun, 2007 1 commit
-
-
unknown authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/jun05/50 mysql-test/mysql-test-run.pl: Auto merged mysql-test/t/mysqltest.test: Auto merged sql/mysql_priv.h: Auto merged sql/mysqld.cc: Auto merged sql/sql_parse.cc: Auto merged sql/sql_table.cc: Auto merged sql/sql_yacc.yy: Auto merged
-
- 04 Jun, 2007 3 commits
- 03 Jun, 2007 1 commit
-
-
unknown authored
into amd64.(none):/src/bug24732/my50-bug24732
-
- 02 Jun, 2007 1 commit
-
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.0-maint client/mysqltest.c: Auto merged
-
- 01 Jun, 2007 16 commits
-
-
unknown authored
- Cleanup typo. - Make sure to only embedded four part numberic version. CMakeLists.txt: Bug #24732 Executables do not include Vista manifests - Correct typo in manifest detection logic. win/create_manifest.js: Bug #24732 Executables do not include Vista manifests - Remove -* from the end of version string before embedding into manifest.
-
unknown authored
-
unknown authored
Problem: we may create a deadlock committing changes in the mysql_alter_table() when LOCK_open is set. Moreover, "in some variants of the ALTER TABLE commit happens earlier, outside of LOCK_open, in other later - inside. It's no good, a storage engine code that is called in between could expect a consistency - either there is a transaction or there is not". Fix: move the commit to happen earlier and outside of the LOCK_open. mysql-test/r/innodb_mysql.result: Fix for bug #28652: MySQL (with-debug=full) asserts when alter table operations - test result. mysql-test/t/innodb_mysql.test: Fix for bug #28652: MySQL (with-debug=full) asserts when alter table operations - test case. sql/sql_table.cc: Fix for bug #28652: MySQL (with-debug=full) asserts when alter table operations - commit moved to happen earlier in the mysql_alter_table(), now we commit changes at the same time as in case when a temporary table is used.
-
unknown authored
-
unknown authored
-
unknown authored
mysql-test/r/rpl_loaddata.result: Update result. mysql-test/t/rpl_loaddata.test: Fix a typo in the test file.
-
unknown authored
mysql-test/r/sp.result: Update results. mysql-test/t/mysql.test: Fix a typo. mysql-test/t/mysqltest.test: Fix a typo. mysql-test/t/order_by.test: Fix a typo. mysql-test/t/row.test: Remove an unsupported command. mysql-test/t/sp.test: Fix a typo. mysql-test/t/subselect3.test: Fix mysqltest warnings - now it warns when sees some suspicious -- comment
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.0-maint mysql-test/r/mysqltest.result: Auto merged mysql-test/t/mysqltest.test: Auto merged
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.0-maint
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.0-maint
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-5.0-maint
-
unknown authored
into pilot.(none):/data/msvensson/mysql/mysql-4.1-maint
-
unknown authored
-
unknown authored
-
unknown authored
into pilot.(none):/data/msvensson/mysql/bug28497/my50-bug28497 client/mysqltest.c: Auto merged mysql-test/r/mysqltest.result: Auto merged mysql-test/t/mysqltest.test: Auto merged
-
unknown authored
- Add funtion "query_get_value to allow reading a fields value into a $variable client/mysqltest.c: - Add function "let $var= query_get_value(<query>,<colname>,<row>)" making it possible to read a value from a specific field in a query into a $variable. mysql-test/r/mysqltest.result: Add test cases for "query_get_value" mysql-test/t/mysqltest.test: Add test cases for "query_get_value"
-
- 31 May, 2007 5 commits
-
-
unknown authored
- Update tests to be independent how the mysqld was started mysql-test/r/mysqltest.result: Update result file mysql-test/t/mysqltest.test: The purpose of these three test is to check that "sync_with_master" detects illegal parameters, the parameter checking is done before sending any command to the server and the "save_master_pos" can be removed in two cases to make the tests independent of mysqld. The thirs test is removed since it's a syntax check that is done after the command has been executed and is done for all comands in mysqltest - it's tested elsewhere and is not specific to "sync_with_master"
-
unknown authored
into polly.local:/home/kaa/src/maint/mysql-5.0-maint sql/sql_select.cc: Auto merged
-
unknown authored
Problem: HASH indexes on VARCHAR columns with binary collations did not ignore trailing spaces from strings before comparisons. This could result in duplicate records being successfully inserted into a MEMORY table with unique key constraints. As a direct consequence of the above, internal MEMORY tables used for GROUP BY calculation in testcases for bug #27643 contained duplicate rows which resulted in duplicate key errors when converting those temporary tables to MyISAM. Additionally, that error was incorrectly converted to the 'table is full' error. Solution: - ignore trailing spaces in VARCHAR fields with binary collations when calculating hashes. - return a proper error from create_myisam_from_heap() when conversion fails. mysql-test/r/ctype_ucs2_def.result: Added a testcase for bug #27643. mysql-test/r/heap_hash.result: Added a testcase for bug #27643. mysql-test/t/ctype_ucs2_def.test: Added a testcase for bug #27643. mysql-test/t/heap_hash.test: Added a testcase for bug #27643. sql/sql_select.cc: Return an appropriate error instead of 'table is full' when conversion from MEMORY to MyISAM fails. strings/ctype-bin.c: Added my_hash_sort_8bit_bin() which ignores trailing spaces when calculating hashes, and is now used for VARCHAR columns instead of my_hash_sort_bin(). strings/ctype-mb.c: Ignore trailing spaces when calculating a string hash in my_hash_sort_mb_bin(). strings/ctype-ucs2.c: Ignore trailing spaces when calculating a string hash in my_hash_sort_ucs2_bin().
-
unknown authored
into polly.local:/home/kaa/src/maint/mysql-5.0-maint strings/strtod.c: Auto merged
-
unknown authored
into mysql.com:/nfsdisk1/lars/bk/mysql-5.0-rpl mysql-test/t/disabled.def: Auto merged
-
- 30 May, 2007 8 commits
-
-
unknown authored
Fix harmless typo (caught thanks to warning) client/mysqldump.c: Fix harmless typo (caught thanks to warning)
-
unknown authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/50 strings/strtod.c: Auto merged
-
unknown authored
into quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/41
-
unknown authored
into damien-katzs-computer.local:/Users/dkatz/50_dump
-
unknown authored
refining the test because of Bug #28786 'reset master' does not reset binlogging on embeded server mysql-test/t/binlog_killed.test: the test can not pass on embedded server. Setting the include-guard.
-
unknown authored
Got rid of log_01[], because we don't really need it. Division and log_10[] can always be used instead, which is also a more precise way. This is for bug #28121. include/m_string.h: Got rid of log_01[], because we don't really need it. sql/item_cmpfunc.cc: Got rid of log_01[], because we don't really need it. strings/strtod.c: Got rid of log_01[], because we don't really need it.
-
unknown authored
test comments correction mysql-test/r/binlog_killed.result: changed mysql-test/t/binlog_killed.test: wrong comments (but important ones) left; little refinement in result calc
-
unknown authored
-
- 29 May, 2007 5 commits
-
-
unknown authored
combining the final result variable in such way that either option of the test execution will yield zero. mysql-test/r/binlog_killed.result: results changed mysql-test/t/binlog_killed.test: there are two options for the test passing: 1. no rows inserted and the INSERT gets killed, then there is no INSERT query in binlog 2. all rows inserted, then INSERT gets to binlog and error_code is zero
-
unknown authored
tests refining, see binlog_killed.test file for details mysql-test/r/binlog_killed.result: results changed mysql-test/t/binlog_killed.test: killer conn waits for the first row to appear; log-disabling kill query since prey's id is not deterministic; correcting pattern to search in binlog for insert query;
-
unknown authored
refining the test. mysql-test/t/binlog_killed.test: due to killing reap may catch an error though it's indeterministic.
-
unknown authored
result file updated mysql-test/r/binlog_killed.result: results updated
-
unknown authored
Refining the tests since pb revealed the older version's fragality - the error from SF() due to killed may be different on different env:s. DBUG_ASSERT instead of assert. mysql-test/r/binlog_killed.result: new result file mysql-test/t/binlog_killed.test: regression for bug#22725 simplified. tests for bug27563, BUG#27565 made inactive. sql/sql_insert.cc: DBUG_ASSERT
-