An error occurred fetching the project authors.
- 18 Mar, 2008 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
binlog_format=mixed Statement-based replication of DELETE ... LIMIT, UPDATE ... LIMIT, INSERT ... SELECT ... LIMIT is not safe as order of rows is not defined. With this fix, we issue a warning that this statement is not safe to replicate in statement mode, or go to row-based mode in mixed mode. Note that we may consider a statement as safe if ORDER BY primary_key is present. However it may confuse users to see very similiar statements replicated differently. Note 2: regular UPDATE statement (w/o LIMIT) is unsafe as well, but this patch doesn't address this issue. See comment from Kristian posted 18 Mar 10:55.
-
- 11 Jan, 2008 1 commit
-
-
mkindahl@dl145h.mysql.com authored
-
- 19 Jun, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
-
- 01 Jun, 2007 1 commit
-
-
mats@kindahl-laptop.dnsalias.net authored
-
- 14 May, 2007 1 commit
-
-
mats@romeo.kindahl.net authored
Replacing binlog_row_based_if_mixed with variable binlog_stmt_flags holding several flags and adding member functions to manipulate the flags. Added code to generate a warning when an attempt to log an unsafe statement to the binary log was made. The warning is both pushed to the SHOW WARNINGS table and written to the error log. The prevent flooding the error log, the warning is just written to the error log once per open session.
-