An error occurred fetching the project authors.
- 21 Feb, 2005 1 commit
-
-
lars@mysql.com authored
-
- 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.
-
- 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)
-
- 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
-
- 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.
-