An error occurred fetching the project authors.
- 20 Feb, 2007 1 commit
-
-
kaa@polly.local authored
-
- 19 Feb, 2007 2 commits
-
-
msvensson@pilot.blaudden authored
way
-
kaa@polly.local authored
The problem happened because those tests were using "cp932" and "ucs2" without checking whether these character sets are available. This fix moves test parts to make character set specific parts be tested only if they are: - some parts were moved to "ctype_ucs.test" and "ctype_cp932.test" - some parts were moved to the newly added tests "innodb-ucs2.test", "mysqlbinglog-cp932.test" and "sp-ucs2.test"
-
- 22 Jan, 2007 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
Fixed wrong merge that disabled 'make test' Renamed all suppress files to end in '.supp' Don't give "skipped %d bytes from file" warnings in 5.0
-
- 22 Dec, 2006 1 commit
-
-
- 14 Dec, 2006 3 commits
-
-
monty@mysql.com/narttu.mysql.fi authored
- Removed not used variables and functions - Added #ifdef around code that is not used - Renamed variables and functions to avoid conflicts - Removed some not used arguments Fixed some class/struct warnings in ndb Added define IS_LONGDATA() to simplify code in libmysql.c I did run gcov on the changes and added 'purecov' comments on almost all lines that was not just variable name changes
-
-
Problem: mysqlbinlog_base64 failed sporadically. Reason: Missing "flush logs" before running $MYSQL_BINLOG, which could start dumping the log file before server has finished writting into it. Fix: - implementing --force-if-open option to "mysqlbinlog" - adding --disable-force-if-open to make $MYSQL_BINLOG fail on non-closed log files, to garantee that nobody will forget "flush logs" in the future. - adding "flush logs" into all affected tests.
-
- 07 Dec, 2006 1 commit
-
-
Implementing event based replication of LC_TIME_NAMES for 5.0 (as a replacement of previously made ONE_SHOT replication)
-
- 28 Nov, 2006 1 commit
-
-
Problem: when loading mysqlbinlog dumps, CREATE PROCEDURE having semicolons in their bodies failed. Fix: Using safe delimiter "/*!*/;" to dump log entries.
-
- 30 Aug, 2006 1 commit
-
-
aelkin/elkin@andrepl.dsl.inet.fi authored
The following is an excerption from the WL. 1. Change so that MIXED is default format 1.1 to change the default for command line --binlog-format 1.2 to alter global_system_variables.binlog_format calculation basing on command line --binlog-format parameter and its default. 2. Change test suite so that more testing is done by MIXED format. 2.1 to check if there are test cases requiring --binlog-foramt=statement via `source include/have_binlog_format_statement.inc' and affected by altering the latter to be "mixed". 2.2 to check the content of such vulnerable cases to find if extending to the mixed does not modify results. In that case simply substitute source arguments as explained. 2.3 if a test in mixed mode deals with features triggering row-binlogging then if necessary we can switch explicitly to statement mode or create another test to run with non-recommended STATEMENT mode Particullarily, extracting INSERT DELAYED binlogging subtest for statement mode is performed, and the snippet is moved into a separate test file. Note that since now all three modes verify this use case through 3 different tests. No changes in item 3 of HLD appeared to be needed.
-
- 26 Jul, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
- Modify test case to workaround the test tool problem - (Null merge into 5.0)
-
- 24 Jul, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
- Send confusing output to /dev/null
-
- 31 May, 2006 2 commits
-
-
aelkin@dl145k.mysql.com authored
adapting to pushbuild's custom to switch from default pathes. The name for var directory must be set with MYSQLTEST_VARDIR.
-
aelkin@dl145k.mysql.com authored
missed table to drop after merge from 4.1
-
- 28 May, 2006 1 commit
-
-
aelkin@mysql.com authored
refining the test case to exclude problems with koi8r on some platforms.
-
- 20 May, 2006 1 commit
-
-
aelkin@mysql.com authored
fixing an issue with the test portability.
-
- 16 May, 2006 1 commit
-
-
lars@mysql.com authored
-
- 14 May, 2006 1 commit
-
-
aelkin@mysql.com authored
fixing names length. Got an issue when merged to 5.0, decided to fix starting from 4.1
-
- 13 May, 2006 1 commit
-
-
aelkin@mysql.com authored
fixing a path to find charset by $MYSQL client. I believe the fix is done what should be by default.
-
- 09 May, 2006 1 commit
-
-
aelkin@mysql.com authored
Binlog lacks encoding info about DROPped temporary table. Idea of the fix is to switch temporary to system_charset_info when a temporary table is DROPped for binlog. Since that is the server, that automatically, but not the client, who generates the query the binlog should be updated on the server's encoding for the coming DROP. The `write_binlog_with_system_charset()' is introduced to replace similar problematic places in the code.
-
- 10 Feb, 2006 1 commit
-
-
aelkin@mysql.com authored
This changeset is assumed to stay in 4.1.
-
- 09 Feb, 2006 1 commit
-
-
aelkin@mysql.com authored
internal charset to one associated with currently being handled query. To note such a query can come from interactive client either. There was a discussion within replication team and Monty who's suggestion won. It avoids straightforward parsing of all `set' queries that could affect client side character set. According to the idea, mysql client does not parse `set' queries but rather cares of `charset new_cs_name' command. This command is generated by mysqlbinlog in form of exclaiming comment (Lars' suggestion) so that enlightened clients like `mysql' knows what to do with it. Interactive human can switch between many multi-byte charsets during the session providing the command explicitly. To note that setting new internal mysql's charset does not trigger sending any `SET' sql statement to the server.
-
- 24 Jan, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 22 Dec, 2005 1 commit
-
-
lars@mysql.com authored
This includes both code and test cases.
-
- 24 Sep, 2005 1 commit
-
-
kent@mysql.com authored
Windows have no 'cat' command, use < mysql.test: Windows can't handle single quotes in --exec line
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 30 Mar, 2005 1 commit
-
-
jimw@mysql.com authored
by adding check for embedded server within tests and splitting some tests into multiple test files.
-
- 25 Mar, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4 are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE. If slave fails in Execute_load_query_log_event::exec_event(), don't delete the file (so that it's re-usable at next START SLAVE). And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not executed at all on the slave" (storing an Execute_load_query_log_event to binlog, with its error code, instead of Delete_file_log_event).
-
- 16 Mar, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
Now one can use user variables as target for data loaded from file (besides table's columns). Also LOAD DATA got new SET-clause in which one can specify values for table columns as expressions. For example the following is possible: LOAD DATA INFILE 'words.dat' INTO TABLE t1 (a, @b) SET c = @b + 1; This patch also implements new way of replicating LOAD DATA. Now we do it similarly to other queries. We store LOAD DATA query in new Execute_load_query event (which is last in the sequence of events representing LOAD DATA). When we are executing this event we simply rewrite part of query which holds name of file (we use name of temporary file) and then execute it as usual query. In the beggining of this sequence we use Begin_load_query event which is almost identical to Append_file event
-
- 04 Feb, 2005 1 commit
-
-
mats@mysql.com authored
The utility 'mysqlbinlog' now accepts input from stdin. It can now be used to read the output from, e.g., 'zcat' or other utility.
-
- 16 Jan, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 09 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
binlog even if they changed nothing, and a test for this. This is useful when users use these commands to clean up their master and slave by issuing one command on master (assume master and slave have slightly different data for some reason and you want to clean up both). Note that I have not changed multi-table DELETE and multi-table UPDATE because their error-reporting mechanism is more complicated.
-
- 18 Mar, 2004 1 commit
-
-
guilhem@mysql.com authored
we now detect that the server is sending us a log which we did not request by testing the info in the fake Rotate event. I also changed code to not print the fake Rotate which describes the log we asked for (it's always the first received event but old masters may not send it).
-
- 06 Feb, 2004 1 commit
-
-
vva@eagle.mysql.r18.ru authored
-
- 19 Dec, 2003 1 commit
-
-
guilhem@gbichot2 authored
For previous commit I had run only rpl* tests, here the other ones had a few surprises. Latest status: - all tests pass - all replication tests pass with Valgrind This is the final-final commit & push. Doc remains.
-
- 31 Oct, 2003 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 08 Oct, 2003 3 commits
-
-
vva@eagle.mysql.r18.ru authored
-
monty@narttu.mysql.fi authored
More tests cases After merge fixes
-
monty@narttu.mysql.fi authored
-