- 01 Mar, 2007 9 commits
-
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bkroot/mysql-5.0-rpl
-
rafal@quant.(none) authored
-
bar@mysql.com authored
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bkroot/mysql-5.0-rpl
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bkroot/mysql-5.0-rpl
-
bar@mysql.com authored
when merging into 5.1.
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bk/mysql-5.0-rpl-warnings
-
rafal@quant.(none) authored
-
bar@mysql.com authored
Replacing local directory.
-
- 28 Feb, 2007 7 commits
-
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
bar@mysql.com authored
into mysql.com:/home/bar/mysql-5.0.b24478
-
bar@mysql.com authored
Bug N 15126 character_set_database is not replicated (LOAD DATA INFILE need it) Positions of some binlog events were changed because of additional logging of @@collation_database.
-
bar@mysql.com authored
-
bar@mysql.com authored
into mysql.com:/home/bar/mysql-5.0.b15126
-
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.
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bk/mysql-5.0-bug25306
-
- 27 Feb, 2007 6 commits
-
-
rafal@quant.(none) authored
into quant.(none):/ext/mysql/bk/mysql-5.0-bug25306
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
cbell/Chuck@mysql_cab_desk. authored
SF/Triggers in SBR mode." BUG#14914 "SP: Uses of session variables in routines are not always replicated" BUG#25167 "Dupl. usage of user-variables in trigger/function is not replicated correctly" This patch corrects a minor error in the previous patch for BUG#20141. This patch corrects an errant code change to sp_head.cc. The comments for the first patch follow: User-defined variables used inside of stored functions/triggers in statements which did not update tables directly were not replicated. We also had problems with replication of user-defined variables which were used in triggers (or stored functions called from table-updating statements) more than once. This patch addresses the first issue by enabling logging of all references to user-defined variables in triggers/stored functions and not only references from table-updating statements. The second issue stemmed from the fact that for user-defined variables used from triggers or stored functions called from table-updating statements we were writing binlog events for each reference instead of only one event for the first reference. This problem is already solved for stored functions called from non-updating statements with help of "event unioning" mechanism. So the patch simply extends this mechanism to the case affected. It also fixes small problem in this mechanism which caused wrong logging of references to user-variables in cases when non-updating statement called several stored functions which used the same variable and some of these function calls were omitted from binlog as they were not updating any tables.
-
bar@mysql.com authored
into mysql.com:/home/bar/mysql-5.0.b24478
-
gluh@mysql.com/eagle.(none) authored
-
- 26 Feb, 2007 6 commits
-
-
gbichot@dl145h.mysql.com authored
to the client only after the binlog write and engine commit. No testcase for this bug, as to reproduce it, we need to "kill -9" mysqld, which we cannot do in the testsuite. But, I tested by hand.
-
cbell/Chuck@mysql_cab_desk. authored
into mysql_cab_desk.:C:/source/c++/mysql-5.0-rpl
-
gluh@mysql.com/eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
bar@mysql.com authored
Problem: DROP TRIGGER was not properly handled in combination with slave filters, which made replication stop Fix: loading table name before checking slave filters when dropping a trigger.
-
knielsen@ymer.(none) authored
-
evgen@sunlight.local authored
Post fix for bug#23800.
-
- 25 Feb, 2007 1 commit
-
-
evgen@sunlight.local authored
Post fix for bug#23800. Copy the table name of an Item_outer_ref to the conventional memory.
-
- 24 Feb, 2007 9 commits
-
-
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/23800-bug1-5.0-opt-mysql
-
evgen@moonbone.local authored
Post fix for bug#23800. The Item_field constructor now increases the select_n_where_fields counter. sql_yacc.yy: Post fix for bug#23800. Take into account fields that might be added by subselects. sql_lex.h: Post fix for bug#23800. Added the select_n_where_fields variable to the st_select_lex class. sql_lex.cc: Post fix for bug#23800. Initialization of the select_n_where_fields variable.
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
-
into mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge
-
- 23 Feb, 2007 2 commits
-
-
cbell/Chuck@mysql_cab_desk. authored
into mysql_cab_desk.:C:/source/c++/mysql-5.0_BUG_20141
-
cbell/Chuck@mysql_cab_desk. authored
Triggers in SBR mode." BUG#14914 "SP: Uses of session variables in routines are not always replicated" BUG#25167 "Dupl. usage of user-variables in trigger/function is not replicated correctly" User-defined variables used inside of stored functions/triggers in statements which did not update tables directly were not replicated. We also had problems with replication of user-defined variables which were used in triggers (or stored functions called from table-updating statements) more than once. This patch addresses the first issue by enabling logging of all references to user-defined variables in triggers/stored functions and not only references from table-updating statements. The second issue stemmed from the fact that for user-defined variables used from triggers or stored functions called from table-updating statements we were writing binlog events for each reference instead of only one event for the first reference. This problem is already solved for stored functions called from non-updating statements with help of "event unioning" mechanism. So the patch simply extends this mechanism to the case affected. It also fixes small problem in this mechanism which caused wrong logging of references to user-variables in cases when non-updating statement called several stored functions which used the same variable and some of these function calls were omitted from binlog as they were not updating any tables.
-