- 27 Aug, 2007 17 commits
-
-
tsmith@ramayana.hindu.god authored
Initialize thd->variables.pseudo_thread_id when a new embedded thd is created.
-
tsmith@ramayana.hindu.god authored
into ramayana.hindu.god:/home/tsmith/m/bk/51-target22-X
-
tsmith@ramayana.hindu.god authored
Update some tests in the "parts" suite, so they're skipped if the requisite plugins are not present in the mysqld.
-
tsmith@ramayana.hindu.god authored
Bug #30316: Some "parts" tests fail because the server uses "--secure-file-priv" Bug #30341: Test suite "parts" needs to be adapted to the new rules disallowing many functio Bug #30408: Suite "parts" needs bug numbers updated Bug #30411: Suite "parts" needs bug numbers updated: ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF Bug #30576: part_supported_sql_func_innodb.test tries to LOAD DATA outside of var dir Bug #30581: partition_value tests use disallowed CAST() function Included are some general fixes to allow the "parts" test suite to be run successfully. This includes disabling a few tests or parts of tests, cleaning up the test cases and their results, etc. Basically, these tests have not been run for some time, and had suffered some bit rot. The bugs were fixed as a single changeset, because in some ways they depend on each other. I couldn't be sure I'd updated all the error codes (for bugs 30408 and 30411) without also adapting to the new allowed functions rules (bug 30341), and vice versa.
-
tsmith@ramayana.hindu.god authored
A local variable may be used uninitialized in ha_partition::get_auto_increment(). Initialize it properly.
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-target-5.1.22
-
tomas@whalegate.ndb.mysql.com authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/work/mysql-5.1-target-5.1.22-joro
-
gkodinov/kgeorge@magare.gmz authored
re-pushing for 5.1.22.
-
joerg@trift2. authored
into trift2.:/MySQL/M51/target-5.1.22
-
joerg@trift2. authored
into trift2.:/MySQL/M51/target-5.1.22
-
joerg@trift2. authored
1) "test_db.sql" is a plaintext file, no binary; 2) do not try to strip the binaries, it will not work.
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-target-5.1.22
-
tomas@whalegate.ndb.mysql.com authored
-
gkodinov/kgeorge@magare.gmz authored
MySQL replicates the time zone only when operations that involve it are performed. This is controlled by a flag. But this flag is set only on successful operation. The flag must be set also when there is an error that involves a timezone (so the master would replicate the error to the slaves).
-
gkodinov/kgeorge@magare.gmz authored
A test case was waiting for a fixed number of seconds for a specific state of the slave IO thread to take place. Fixed by waiting in a loop for that specific thread state instead (or timeout).
-
gkodinov/kgeorge@magare.gmz authored
keep_files_on_create made a startup option
-
- 25 Aug, 2007 2 commits
-
-
tsmith@ramayana.hindu.god authored
Bug #16979: AUTO_INC lock in InnoDB works a table level lock Add a table level counter that tracks the number of AUTOINC locks that are pending and/or granted on a table. We peek at this value to determine whether a transaction doing a simple INSERT in innodb_autoinc_lock_mode = 1, needs to acquire the AUTOINC lock or not. This change is related to Bug# 16979. Bug #27950: Duplicate entry error in auto-inc after mysqld restart We check whether the AUTOINC sub-system has been initialized (first) by holding the AUTOINC mutex and if initialization is required then we initialize using our normal procedure.
-
tsmith@ramayana.hindu.god authored
Bug #16979: AUTO_INC lock in InnoDB works a table level lock - this is a major change in InnoDB auto-inc handling. Bug #27950: Duplicate entry error in auto-inc after mysqld restart - Init AUTOINC from delete_row(). Bug #28781: InnoDB increments auto-increment value incorrectly with ON DUPLICATE KEY UPDATE - Use value specified by MySQL, in update_row().
-
- 24 Aug, 2007 6 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/target-5.1.22
-
joerg@trift2. authored
into trift2.:/MySQL/M51/netware2-5.1
-
joerg@trift2. authored
1) Ensure "init_db.sql" and "test_db-sql" really get built. 2) Ensure the "*.def" files with NetWare linker options get distributed to the proper directories.
-
holyfoot/hf@mysql.com/hfmain.(none) authored
bug fixed partition_pruning.result: test fixed
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-target-5.1.22
-
tomas@whalegate.ndb.mysql.com authored
-
- 23 Aug, 2007 9 commits
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/target-5.1.22/mysql-5.1-target-5.1.22
-
gshchepa/uchum@gleb.loc authored
Recommit to 5.1.22. The bug caused memory corruption for some queries with top OR level in the WHERE condition if they contained equality predicates and other sargable predicates in disjunctive parts of the condition. The corruption happened because the upper bound of the memory allocated for KEY_FIELD and SARGABLE_PARAM internal structures containing info about potential lookup keys was calculated incorrectly in some cases. In particular it was calculated incorrectly when the WHERE condition was an OR formula with disjuncts being AND formulas including equalities and other sargable predicates.
-
gshchepa/uchum@gleb.loc authored
Recommit to 5.1.22. Killing a SELECT query with KILL QUERY or KILL CONNECTION causes a server crash if the query cache is enabled. Normal evaluation of a query may be interrupted by the KILL QUERY/CONNECTION statement, in this case the mysql_execute_command function returns TRUE, and the thd->killed flag has true value. In this case the result of the query may be cached incompletely (omitting call to query_cache_insert inside the net_real_write function), and next call to query_cache_end_of_result may lead to server crash. Thus, the query_cache_end_of_result function has been modified to abort query cache in the case of killed thread.
-
gshchepa/uchum@gleb.loc authored
Recommit to 5.1.22. The server created temporary tables for filesort in the working directory instead of the specified tmpdir directory.
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-target-5.1.22
-
tomas@whalegate.ndb.mysql.com authored
- let the receiving injector thread decide what to do (recommit for 5.1.22 target)
-
-
jmiller/ndbdev@ndb08.mysql.com authored
into mysql.com:/data1/mysql-5.1-target-5.1.22
-
tomas@whalegate.ndb.mysql.com authored
(recommit for 5.1.22 target)
-
- 22 Aug, 2007 4 commits
-
-
antony@pcg5ppc.xiphis.org authored
"Test federated_bug_25714 issues non-existing shell command" Problem caused by missing '$' symbol in eval statement causing it to always attempt to run test even if the test was not compiled.
-
joerg@trift2. authored
-
Updated test case to correst inconsistant results on different OS per #bug30559
-
joerg@trift2. authored
into trift2.:/MySQL/M51/target-5.1.22
-
- 21 Aug, 2007 1 commit
-
-
uncommented the test case stated in bug18856 and commiting to mysql-5.1-target-5.1.22 clone per Tomas
-
- 20 Aug, 2007 1 commit
-
-
jbruehe/mysqldev@suse9-x86.mysql.com authored
-