An error occurred fetching the project authors.
- 24 Feb, 2009 1 commit
-
-
Andrei Elkin authored
-
- 20 Feb, 2009 1 commit
-
-
Andrei Elkin authored
Signed integer format specifier forced to print the binlog header with server_id negative if the unsigned value sets the sign-bit ON. Fixed with correcting the specifier to correspond to typeof(server_id) == ulong.
-
- 19 Feb, 2009 1 commit
-
-
Patrick Crews authored
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
-
- 16 May, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
-
- 15 May, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
slave The stored-routine code took the contents of the (lowest) parser and copied it directly to the binlog, which causes problems if there is a special case of interpretation at the parser level -- which there is, in the "/*!VER */" comments. The trailing "*/" caused errors on the slave, naturally. Now, since by that point we have /properly/ created parse-tree (as the rest of the server should do!) for the stored-routine CREATE, we can construct a perfect statement from that information, instead of writing uncertain information from an unknown parser state. Fortunately, there's already a function nearby that does exactly that. --- Update for Bug#36570. Qualify routine names with db name when writing to the binlog ONLY if the source text is qualified.
-
- 14 May, 2008 1 commit
-
-
cmiller@zippy.cornsilk.net authored
slave The stored-routine code took the contents of the (lowest) parser and copied it directly to the binlog, which causes problems if there is a special case of interpretation at the parser level -- which there is, in the "/*!VER */" comments. The trailing "*/" caused errors on the slave, naturally. Now, since by that point we have /properly/ created parse-tree (as the rest of the server should do!) for the stored-routine CREATE, we can construct a perfect statement from that information, instead of writing uncertain information from an unknown parser state. Fortunately, there's already a function nearby that does exactly that.
-
- 02 Apr, 2008 1 commit
-
-
sven@riska.(none) authored
Problem: a typo in the code. When autocommit, foreign_key_checks, sql_auto_is_null, or unique_checks changes, it prints "SET", and then a comma-separated list of assignments. However, it does not print the assignment to the @@autocommit variable. Fix: print the @@autocommit variable.
-
- 07 Mar, 2008 1 commit
-
-
sven@riska.(none) authored
Problem: in mixed and statement mode, a query that refers to a system variable will use the slave's value when replayed on slave. So if the value of a system variable is inserted into a table, the slave will differ from the master. Fix: mark statements that refer to a system variable as "unsafe", meaning they will be replicated by row in mixed mode and produce a warning in statement mode. There are some exceptions: some variables are actually replicated. Those should *not* be marked as unsafe. BUG#34732: mysqlbinlog does not print default values for auto_increment variables Problem: mysqlbinlog does not print default values for some variables, including auto_increment_increment and others. So if a client executing the output of mysqlbinlog has different default values, replication will be wrong. Fix: Always print default values for all variables that are replicated. I need to fix the two bugs at the same time, because the test cases would fail if I only fixed one of them.
-
- 01 Feb, 2008 2 commits
-
-
mkindahl@dl145h.mysql.com authored
on the context.
-
mkindahl@dl145h.mysql.com authored
-
- 08 Jan, 2008 1 commit
-
-
msvensson@pilot.mysql.com authored
-
- 17 Dec, 2007 1 commit
-
-
hezx@hezx.(none) authored
fine The reason of this bug is that when mysqlbinlog dumps a query, the query is written to output with a delimeter appended right after it, if the query string ends with a '--' comment, then the delimeter would be considered as part of the comment, if there are any statements after this query, then it will cause a syntax error. Start a newline before appending delimiter after a query string
-
- 15 Dec, 2007 1 commit
-
-
hezx@hezx.(none) authored
The reason of this bug is that when mysqlbinlog dumps a query, the query is written to output with a delimeter appended right after it, if the query string ends with a '--' comment, then the delimeter would be considered as part of the comment, if there are any statements after this query, then it will cause a syntax error. Start a newline before appending delimiter after a query string
-
- 12 Dec, 2007 1 commit
-
-
msvensson@pilot.mysql.com authored
- dynamic configuration support - safe process - cleanups - create new suite for fedarated
-
- 23 Nov, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
The client program 'mysqlbinlog' crashed when trying to print a User_var_log_event holding a floating-point value since the format specifier for my_b_printf() does not support floating-point format specifiers. This patch prints the floating-point number to an internal buffer, and then writes that buffer to the output instead.
-
- 12 Nov, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
Adding missing drop of user created for test case.
-
- 09 Nov, 2007 1 commit
-
-
mats@capulet.net authored
When running mysqlbinlog on a 64-bit machine with a corrupt relay log, it causes mysqlbinlog to crash. In this case, the crash is caused because a request for 18446744073709534806U bytes is issued, which apparantly can be served on a 64-bit machine (speculatively, I assume) but this causes the memcpy() issued later to copy the data to segfault. The request for the number of bytes is caused by a computation of data_len - server_vars_len where server_vars_len is corrupt in such a sense that it is > data_len. This causes a wrap-around, with the the data_len given above. This patch adds a check that if server_vars_len is greater than data_len before the substraction, and aborts reading the event in that case marking the event as invalid. It also adds checks to see that reading the server variables does not go outside the bounds of the available space, giving a limited amount of integrity check.
-
- 03 Nov, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
Adding check that the user executing a BINLOG statement has SUPER privileges and aborting execution of the statement with an error otherwise.
-
- 01 Aug, 2007 1 commit
-
-
restores from mysqlbinlog out Problem: using "mysqlbinlog | mysql" for recoveries the connection_id() result may differ from what was used when issuing the statement. Fix: if there is a connection_id() in a statement, write to binlog SET pseudo_thread_id= XXX; before it and use the value later on.
-
- 20 Jun, 2007 1 commit
-
-
gshchepa/uchum@gleb.loc authored
Occasionally mysqlbinlog --hexdump failed with error: ERROR 1064 (42000) at line ...: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Query thread_id=... exec_time=... error_code=... When the length of hexadecimal dump of binlog header was divisible by 16, commentary sign '#' after header was lost. The Log_event::print_header function has been modified to always finish hexadecimal binlog header with "\n# ".
-
- 02 Apr, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
-
- 31 Mar, 2007 1 commit
-
-
msvensson@pilot.blaudden authored
-
- 07 Mar, 2007 1 commit
-
-
tsmith@quadxeon.mysql.com authored
-
- 01 Mar, 2007 4 commits
-
-
msvensson@pilot.blaudden authored
-
bar@mysql.com authored
-
bar@mysql.com authored
-
bar@mysql.com authored
Replacing local directory.
-
- 28 Feb, 2007 2 commits
-
-
bar@mysql.com authored
-
bar@mysql.com authored
This patch fixes problem that LOAD DATA could use different character sets when loading files on master and on slave sides: - Adding replication of thd->variables.collation_database - Adding optional character set clause into LOAD DATA Note, the second way, with explicit CHARACTER SET clause should be the recommended way to load data using an alternative character set. The old way, using "SET @@character_set_database=xxx" should be gradually depricated.
-
- 19 Feb, 2007 1 commit
-
-
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
-
- 14 Dec, 2006 1 commit
-
-
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.
-
- 31 May, 2006 1 commit
-
-
aelkin@dl145k.mysql.com authored
missed table to drop after merge from 4.1
-
- 16 May, 2006 1 commit
-
-
lars@mysql.com authored
-
- 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
-