summaryrefslogtreecommitdiff
path: root/mysql-test/include
Commit message (Collapse)AuthorAgeFilesLines
* BUG#45516 SQL thread does not use database charset properly2009-08-121-0/+35
| | | | | | | | | | Replication SQL thread does not set database default charset to thd->variables.collation_database properly, when executing LOAD DATA binlog. This bug can be repeated by using "LOAD DATA" command in STATEMENT mode. This patch adds code to find the default character set of the current database then assign it to thd->db_charset when slave server begins to execute a relay log. The test of this bug is added into rpl_loaddata_charset.test
* Post-fix for BUG#43264Alfranio Correia2009-08-031-0/+481
| | | | Install procedure does not copy *.inc files located under the mysql-test/t directory. Therefore, this patch moves the rpl_trigger.inc to the mysql-test/include directory.
* Bug#40465 - mysqldump.test does no checking of dump or restorePatrick Crews2009-05-221-3/+12
| | | | | | | | | | | Created new .test file - mysqldump_restore that does test restore from mysqldump output for a limited number of basic cases. Create new .inc file - mysqldump.inc - renames original table and uses mysqldump output to recreate the table, then uses diff_tables.inc to compare the two tables. Backported include/diff_tables.inc to facilitate this testing. New patch incorporating review feedback prior to push. mysqldump.test - removed redundant call to include/have_log_bin.inc (was used twice in the test!)
* Bug#40465: mysqldump.test does no checking of dump or restore.Patrick Crews2009-05-212-0/+163
| | | | | | | Created new .test file - mysqldump_restore that does this for a limited number of basic cases. Created new .inc file - mysqldump.inc - renames original table and uses mysqldump output to recreate the table, then uses diff_tables.inc to compare the two tables. Backported include/diff_tables.inc to facilitate this testing.
* Merge community up to enterprise, thus ending the community-serverChad MILLER2009-05-062-0/+8
|\ | | | | | | adventure.
| * Pull 5.1 treatment of community features into 5.0.Chad MILLER2009-05-052-0/+8
| |
* | BUG#37145 Killing a statement doing DDL may log binlog event with error code ↵He Zhenxing2009-03-273-0/+132
|/ | | | | | | | | | | | | | | | | | | | 1053 When the thread executing a DDL was killed after finished its execution but before writing the binlog event, the error code in the binlog event could be set wrongly to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED. This patch fixed the problem by ignoring the kill status when constructing the event for DDL statements. This patch also included the following changes in order to provide the test case. 1) modified mysqltest to support variable for connection command 2) modified mysql-test-run.pl, add new variable MYSQL_SLAVE to run mysql client against the slave mysqld.
* Automerge.Alexey Kopytov2009-03-241-0/+21
|\
| * Fix for bug #43801: mysql.test takes too long, fails due to Alexey Kopytov2009-03-241-0/+21
| | | | | | | | | | | | | | expired timeout on debx86-b in PB Moved the resource-intensive test case for bug #41486 into a separate test file to reduce execution time for mysql.test.
* | Bug#41307: Tests using include/ndb_backup.inc won't work on Windows due to ↵Patrick Crews2009-03-151-14/+34
| | | | | | | | | | | | | | | | 'grep' call. Revised patch incorporating cleaner test code brought up during review. Removed the use of grep and accomplished same actions via SQL / use of the server. Runs as before on *nix systems and now runs on Windows without Cygwin as well.
* | Merge of fix into actual treeMatthias Leich2009-03-101-10/+23
|\ \
| * \ Merge of fix for Bug#42003 and Bug#43114 into more actual GCA treeMatthias Leich2009-03-051-10/+23
| |\ \ | | |/ | |/| modifications according to the reviews are included
| | * Last slice of fix for Bug#42003 tests missing the disconnect of connections ↵Matthias Leich2009-03-031-10/+23
| | | | | | | | | | | | | | | | | | | | | <> default + Fix for Bug#43114 wait_until_count_sessions too restrictive, random PB failures + Removal of a lot of other weaknesses found + modifications according to review
* | | BUG#37051 Replication rules not evaluated correctlyHe Zhenxing2009-03-055-0/+127
|/ / | | | | | | Backporting patch to 5.0.
* | automergePatrick Crews2009-02-201-0/+78
|\ \
| * | Bug #42419: test suite fixGeorgi Kodinov2009-02-201-0/+78
| |/ | | | | | | | | Moved the test case for the bug into a separate file (and restored the original innodb_mysql test setup). Used the new wait_show_condition test macro to avoid the usage of sleep
* | Bug#38831: 11 test cases fail on Windows due to missing commandsPatrick Crews2009-02-191-0/+7
|/ | | | | | Replaced Unix calls with mysql-test-run's built-in functions / SQL manipulation where possible. Replaced error codes with error names as well. Disabled two tests on Windows due to more complex Unix command usage See Bug#41307, Bug#41308
* This belongs to the fix forMatthias Leich2009-02-091-1/+2
| | | | | | | | | | | | | | | | Bug#42003 tests missing the disconnect of connections <> default second slice Content: 1. wait_until_count_sessions.inc - One PB run of a test using this routine failed because 5 seconds timeout were exceeded. Although I have some doubts if the assigned timeout was really too small, I increase the value to 10. We waste the additional 5 seconds only if the tests fails anyway. - Print the content of the PROCESSLIST if the poll routine fails 2. minor improvements of formatting 3. query_cache_notembedded: Activate the wait_until_count_sessions.inc routine which was unfortunately forgotten in the changeset before.
* 1. Slice of fix for Bug#42003 tests missing the disconnect of connections <> ↵Matthias Leich2009-02-022-0/+133
| | | | | | | | | | | | | | | | | | | | | | default - If missing: add "disconnect <session>" - If physical disconnect of non "default" sessions is not finished at test end: add routine which waits till this happened + additional improvements like - remove superfluous files created by the test - replace error numbers by error names - remove trailing spaces, replace tabs by spaces - unify writing of bugs within comments - correct comments - minor changes of formatting Modifications according to the code review are included. Fixed tests: grant2 grant3 lock_tables_lost_commit mysqldump openssl_1 outfile
* Bug#40866: mysql-test-run's check of tests provides false failures due to ↵Patrick Crews2008-11-241-19/+19
| | | | | | timestamp Altering how MTR checks global variable status to exclude timestamp Changed SQL statements to update style.
* Bug#38311 Some tests use 'rm' which is not portablePatrick Crews2008-09-201-1/+2
| | | | Substituted use of MTR's remove_file function in the tests Started with 5.0 tree and will clean up any offenders discovered during upmerge.
* Bug#30563: Is not possible to create rpl_ or innodb test if needed \Chad MILLER2008-07-0430-31/+31
| | | | | | to use ANSI_QUOTES Make all have_* tests universally safe by using ANSI quotes.
* Fix forMatthias Leich2008-06-251-0/+59
| | | | | Bug#37492 timing bug in subselect.test + similar weaknesses found during testing + replace error numbers by error names
* Merge mkindahl@bk-internal.mysql.com:/home/bk/mysql-5.0mkindahl@dl145h.mysql.com2008-03-312-3/+12
|\ | | | | | | into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
| * Merge mail.hezx.com:/media/sda3/work/mysql/bkroot/mysql-5.0-rplhezx@mail.hezx.com2008-03-261-3/+9
| |\ | | | | | | | | | into mail.hezx.com:/media/sda3/work/mysql/bkwork/b33029_5.0_to_5.1_fails_on_dup_key/5.0
| | * BUG#33029 5.0 to 5.1 replication fails on dup key when insertinghezx@mail.hezx.com2008-03-141-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | using a trig in SP For all 5.0 and up to 5.1.12 exclusive, when a stored routine or trigger caused an INSERT into an AUTO_INCREMENT column, the generated AUTO_INCREMENT value should not be written into the binary log, which means if a statement does not generate AUTO_INCREMENT value itself, there will be no Intvar event (SET INSERT_ID) associated with it even if one of the stored routine or trigger caused generation of such a value. And meanwhile, when executing a stored routine or trigger, it would ignore the INSERT_ID value even if there is a INSERT_ID value available set by a SET INSERT_ID statement. Starting from MySQL 5.1.12, the generated AUTO_INCREMENT value is written into the binary log, and the value will be used if available when executing the stored routine or trigger. Prior fix of this bug in MySQL 5.0 and prior MySQL 5.1.12 (referenced as the buggy versions in the text below), when a statement that generates AUTO_INCREMENT value by the top statement was executed in the body of a SP, all statements in the SP after this statement would be treated as if they had generated AUTO_INCREMENT by the top statement. When a statement that did not generate AUTO_INCREMENT value by the top statement but by a function/trigger called by it, an erroneous Intvar event would be associated with the statement, this erroneous INSERT_ID value wouldn't cause problem when replicating between masters and slaves of 5.0.x or prior 5.1.12, because the erroneous INSERT_ID value was not used when executing functions/triggers. But when replicating from buggy versions to 5.1.12 or newer, which will use the INSERT_ID value in functions/triggers, the erroneous value will be used, which would cause duplicate entry error and cause the slave to stop. The patch for 5.0 fixed it not to generate the erroneous Intvar event, another patch for 5.1 fixed it to ignore the SET INSERT_ID value when executing functions/triggers if it is replicating from a master of buggy versions.
| * | Bug #18199 PURGE BINARY LOGS fails silently with missing logs;aelkin/andrei@mysql1000.(none)2008-03-171-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug #18453 Warning/error message if there is a mismatch between ... There were three problems: 1. the reported lack of warnings for the BEFORE syntax of PURGE; 2. the similar lack of warnings for the TO syntax; 3. incompatible behaviour between the two in that the latter blanked out regardlessly of presence or lack the actual file corresponding to an index record; the former version gave up at the first mismatch. fixed with deploying the warning's generation and synronizing logics of purge_logs() and purge_logs_before_date(). my_stat() is called in either of two branches of purge_logs() (responsible for the TO syntax of PURGE) similarly to how it has behaved in the BEFORE syntax. If there is no actual binlog file, my_stat returns NULL and my_delete is not invoked. A critical error is reported to the user if a file from the index could not be retrieved info about or deleted with a system error code different than ENOENT.
* | | Merge stella.local:/home2/mydev/mysql-5.0-amainistruewing@stella.local2008-03-261-0/+16
|\ \ \ | |/ / |/| | | | | into stella.local:/home2/mydev/mysql-5.0-axmrg
| * | Merge ↵antony@pcg5ppc.xiphis.org2008-03-071-0/+16
| |\ \ | | | | | | | | | | | | | | | | | | | | pcg5ppc.xiphis.org:/Network/Servers/anubis.xiphis.org/home/antony/work/mysql-5.0-engines into pcg5ppc.xiphis.org:/Network/Servers/anubis.xiphis.org/home/antony/work/merge.20080307/mysql-5.0
| | * \ Merge mysql.com:/home/bar/mysql-work/mysql-5.0.b27580bar@bar.myoffice.izhnet.ru2008-03-061-0/+16
| | |\ \ | | | |/ | | |/| | | | | into mysql.com:/home/bar/mysql-work/mysql-5.0.b27580v2
| | | * Bug#27580 SPACE() function collation bug?bar@mysql.com/bar.myoffice.izhnet.ru2007-10-081-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: when character_set_connection=utf8, mixing SPACE() with a non-Unicode column (e.g. for concat) produced "illegal mix of collations" error. Fix: Item_string() corresponding to space character is now created using "ASCII" repertoire. Previously it was incorrectly created using "UNICODE" repertoure, which didn't allow to convert results of SPACE() to a non-Unicode character set.
* | | | Merge dl145h.mysql.com:/data0/mkindahl/mysql-5.0mkindahl@dl145h.mysql.com2008-02-271-0/+25
|\ \ \ \ | |/ / / |/| | | | | | | into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl
| * | | Merge mysql.com:/home/bar/mysql-work/mysql-5.0.b32510bar@bar.myoffice.izhnet.ru2008-02-201-0/+25
| |\ \ \ | | |/ / | |/| | | | | | into mysql.com:/home/bar/mysql-work/mysql-5.0.b32510v2
| | * | Bug#32510 LIKE search fails with indexed 'eucjpms' and 'ujis' char columnbar@mysql.com/bar.myoffice.izhnet.ru2008-02-041-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: some collation handlers called incorrect version of my_like_range_xxx(), which led to wrong min_str and max_str, so like range optimizer threw away good records. Fix: changing the wrong handlers to call proper version of my_like_range_xxx().
* | | | Bug#32025 ndb_waiter does too many roundtrips to ndb_mgmdmsvensson@pilot.mysql.com2008-02-211-0/+26
|/ / / | | | | | | | | | | | | | | | - fix test failures that was already there but now are more consistent when the 1 second sleep has been removed from ndb_waiter
* | | Changes to fix tests in pushbuild.mkindahl@dl145h.mysql.com2008-01-311-0/+4
| | |
* | | Merge dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rplmkindahl@dl145h.mysql.com2008-01-301-0/+5
|\ \ \ | |/ / | | | | | | into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
| * | Add missing include test file for rpl_server_id testhezx@mail.hezx.com2008-01-061-0/+5
| | |
* | | Merge mysql.com:/home/gluh/MySQL/Merge/5.0gluh@eagle.(none)2007-12-131-2/+2
|\ \ \ | | | | | | | | | | | | into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
| * | | Bug #32400: Complex SELECT query returns correct result gkodinov/kgeorge@magare.gmz2007-11-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | only on some occasions Referencing an element from the SELECT list in a WHERE clause is not permitted. The namespace of the WHERE clause is the table columns only. This was not enforced correctly when resolving outer references in sub-queries. Fixed by not allowing references to aliases in a sub-query in WHERE.
* | | | Merge mysql.com:/home/ram/work/mysql-5.0-enginesramil/ram@ramil.myoffice.izhnet.ru2007-11-291-0/+2
|\ \ \ \ | | | | | | | | | | | | | | | into mysql.com:/home/ram/work/b32726/b32726.5.0
| * | | | Fix for bug #32726: crash with cast in order by clause and cp932 charsetramil/ram@mysql.com/ramil.myoffice.izhnet.ru2007-11-281-0/+2
| |/ / / | | | | | | | | | | | | | | | | - fix for #31070 (missed during merging) applied for cp932 charset. - tests/results adjusted.
* | | | Merge dl145h.mysql.com:/data0/mkindahl/mysql-5.0mkindahl@dl145h.mysql.com2007-11-211-0/+42
|\ \ \ \ | |/ / / |/| / / | |/ / into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
| * | Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-5.0bar@bar.myoffice.izhnet.ru2007-10-301-0/+42
| |\ \ | | | | | | | | | | | | into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl-merge
| | * \ Merge mysql.com:/home/bar/mysql-work/mysql-5.0bar@bar.myoffice.izhnet.ru2007-10-241-0/+42
| | |\ \ | | | | | | | | | | | | | | | into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl-mr
| | | * | Bug#31081 server crash in regexp functionbar@mysql.com/bar.myoffice.izhnet.ru2007-10-051-0/+42
| | | |/ | | | | | | | | | | | | | | | | | | | | | | | | Problem: The "regex" library written by Henry Spencer does not support tricky character sets like UCS2. Fix: convert tricky character sets to UTF8 before calling regex functions.
* | | | Bug#31909 - New gis.test creates warnings filesistruewing@stella.local2007-11-011-8/+8
|/ / / | | | | | | | | | | | | | | | | | | Comment sign of -- at line begin in test files lead to warnings from mysqltest. Changed -- to #.
* | | Merge mysql.com:/home/gluh/MySQL/Merge/5.0gluh@eagle.(none)2007-10-231-0/+46
|\ \ \ | |/ / |/| | | | | into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
| * | Bug #30825: Problems when putting a non-spatial index on a GIS columngkodinov/kgeorge@magare.gmz2007-10-101-0/+46
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed the usage of spatial data (and Point in specific) with non-spatial indexes. Several problems : - The length of the Point class was not updated to include the spatial reference system identifier. Fixed by increasing with 4 bytes. - The storage length of the spatial columns was not accounting for the length that is prepended to it. Fixed by treating the spatial data columns as blobs (and thus increasing the storage length) - When creating the key image for comparison in index read wrong key image was created (the one needed for and r-tree search, not the one for b-tree/other search). Fixed by treating the spatial data columns as blobs (and creating the correct kind of image based on the index type).
* | Merge mysql.com:/home/ram/work/b31070/b31070.4.1ramil/ram@ramil.myoffice.izhnet.ru2007-10-041-0/+9
|\ \ | | | | | | | | | into mysql.com:/home/ram/work/b31070/b31070.5.0
View Lorry Controller Status