An error occurred fetching the project authors.
- 14 Dec, 2007 1 commit
-
-
sven@riska.(none) authored
Now, every transaction (including autocommit transactions) starts with a BEGIN and ends with a COMMIT/ROLLBACK in the binlog. Added a test case, and updated lots of test case result files.
-
- 09 Oct, 2007 1 commit
-
-
Updated NDB test to run for both RBR and MBR testing. In addition added test for Innodb and updated results files for all tests.
-
- 27 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Update mysql-test-run.pl to collect tests from several suites - Group test into suites - Add suite.opt file
-
- 30 Mar, 2007 1 commit
-
-
mats@romeo.(none) authored
- Eliminating some compiler warnings
-
- 29 Mar, 2007 1 commit
-
-
mats@romeo.(none) authored
Adding an event that can be used to denote that an incident occured on the master. The event can be used to denote a gap in the replication stream, but can also be used to denote other incidents. In addition, the injector interface is extended with functions to generate an incident event. The function will also rotate the binary log after generating an incident event to get a fresh binary log.
-
- 12 Feb, 2007 1 commit
-
-
mats@romeo.(none) authored
does not work): Changing packed row format to only include null bits for those columns that are present in the row as well as writing BIT columns in a storage engine-independent format. The change in row format is incompatible with the previous format and a slave will not be able to read the new events.
-
- 31 May, 2006 1 commit
-
-
mats@mysql.com authored
Switched to writing out table maps for tables that are locked when the first row in a statement is seen.
-
- 10 Mar, 2006 1 commit
-
-
lars@mysql.com authored
-
- 24 Feb, 2006 1 commit
-
-
mats@mysql.com authored
Adaptions to make it work with NDB.
-
- 16 Feb, 2006 1 commit
-
-
mats@mysql.com authored
Table maps are now written on aquiring locks to tables and released at the end of each logical statement.
-
- 22 Dec, 2005 1 commit
-
-
lars@mysql.com authored
This includes both code and test cases.
-
- 30 Sep, 2005 1 commit
-
-
guilhem@mysql.com authored
Tell the user that this ROLLBACK is added by mysqlbinlog (so that he does not wonder if it's present in binlog). This was brought up by Salle - thanks Salle.
-
- 21 Sep, 2005 1 commit
-
-
lars@mysql.com authored
-
- 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
-
- 23 Feb, 2005 1 commit
-
-
guilhem@mysql.com authored
pushed some minutes ago)
-
- 21 Feb, 2005 1 commit
-
-
lars@mysql.com authored
-
- 17 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 16 Feb, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 03 Feb, 2005 1 commit
-
-
guilhem@mysql.com authored
we store 7 bytes (1 + 2*3) in every Query_log_event. In the future if users want binlog optimized for small size and less safe, we could add --binlog-no-charset (and binlog-no-sql-mode etc): charset info is something by design optional (even if for now we don't offer possibility to disable it): it's not a binlog format change. We try to reduce the number of get_charset() calls in the slave SQL thread to a minimum by caching the charset read from the previous event (which will often be equal to the one of the current event). We don't use SET ONE_SHOT for charset-aware repl (we still do for timezones, will be fixed later). No more errors if one changes the global value of charset vars on master or slave (as we log charset info in all Query_log_event). Not fixing Load_log_event as it will be rewritten soon by Dmitri. Testing how mysqlbinlog behaves in rpl_charset.test. mysqlbinlog needs to know where charset file is (to be able to convert a charset number found in binlog (e.g. in User_var_log_event) to a charset name); mysql-test-run needs to pass the correct value for this option to mysqlbinlog. Many result udpates (adding charset info into every event shifts log_pos in SHOW BINLOG EVENTS). Roughly the same job is to be done for timezones :)
-
- 16 Jan, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 06 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Fixed compiler warnings Fix core dump when sending SIGHUP to mysqld
-
- 03 Dec, 2004 1 commit
-
-
mats@mysql.com authored
CREATE DATABASE statement used the current database instead of the database created when checking conditions for replication. CREATE/DROP/ALTER DATABASE statements are now replicated based on the manipulated database.
-
- 03 Nov, 2004 1 commit
-
-
monty@mysql.com authored
FOUND is not a reserved keyword anymore Added Item_field::set_no_const_sub() to be able to mark fields that can't be substituted Added 'simple_select' method to be able to quickly determinate if a select_result is a normal SELECT Note that the 5.0 tree is not yet up to date: Sanja will have to fix multi-update-locks for this merge to be complete
-
- 20 Oct, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
net_printf/send_error calls replaced by my_error family functions -1/1 (sent/unsent) error reporting removed (WL#2133)
-
- 23 Sep, 2004 1 commit
-
-
guilhem@mysql.com authored
we do not increment rli->group_master_log_pos if we are just after a SET ONE_SHOT (it's not a standalone event)
-
- 09 Sep, 2004 1 commit
-
-
monty@mysql.com authored
Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset Prefix addresses with 0x for easier comparisons of debug logs Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index This fix changed some 'index' queries to 'range' queries in the test suite Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause. This fix removed of a lot of 'Using where' notes in the test suite. Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS Give NOTE instead of WARNING for safe field-type conversions
-
- 31 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Use 'mysqltest' as test database instead of test_$1 or test1,test2 to not accidently delete an important database Safety fix for mailformed MERGE files
-
- 15 Jul, 2004 1 commit
-
-
guilhem@mysql.com authored
Replication of charsets and timezones should shortly be changed to not need ONE_SHOT (but 5.0 should still be able to read it, to be able to replicate 4.1 masters).
-
- 06 Jul, 2004 1 commit
-
-
bar@mysql.com authored
An addition to 1.2036 04/07/02: armscii8_bin was referenced to as armscii_bin in a mistake.
-
- 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.
-
- 08 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
In mysqlbinlog, there was a problem with how we escaped the content of a string user variable. To be perfect, we should have escaped with character_set_client. But this charset is unknown to mysqlbinlog. So the simplest is to print the string in hex. This is unreadable but 100% safe with any charset (checked with Bar), no more need to bother with character_set_client.
-
- 03 Jun, 2004 1 commit
-
-
guilhem@mysql.com authored
by binlogging some SET ONE_SHOT CHARACTER_SETetc, which will be enough until we have it more compact and more complete in 5.0. With the present patch, replication will work ok between 4.1.3 master and slaves, as long as: - master and slave have the same GLOBAL.COLLATION_SERVER - COLLATION_DATABASE and CHARACTER_SET_DATABASE are not used - application does not use the fact that table is created with charset of the USEd db (BUG#2326). all of which are not too hard to fulfill. ONE_SHOT is reserved for internal use of mysqlbinlog|mysql and works only for charsets, so we give error if used for non-charset vars. Fix for BUG#3875 "mysqlbinlog produces wrong ouput if query uses variables containing quotes" and BUG#3943 "Queries with non-ASCII literals are not replicated properly after SET NAMES". Detecting that master and slave have different global charsets or server ids.
-