An error occurred fetching the project authors.
- 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.
-
- 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.
-