| Server IP : 172.67.216.182 / Your IP : 104.23.175.245 Web Server : Apache System : Linux krdc-ubuntu-s-2vcpu-4gb-amd-blr1-01.localdomain 5.15.0-142-generic #152-Ubuntu SMP Mon May 19 10:54:31 UTC 2025 x86_64 User : www ( 1000) PHP Version : 7.4.33 Disable Function : passthru,exec,system,putenv,chroot,chgrp,chown,shell_exec,popen,proc_open,pcntl_exec,ini_alter,ini_restore,dl,openlog,syslog,readlink,symlink,popepassthru,pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,imap_open,apache_setenv MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /www/server/mysql/src/mysql-test/suite/rpl/t/ |
Upload File : |
# It's true only in statement-based replication that a statement which # updates no rows (UPDATE/DELETE) is binlogged; in row-based # replication, as we log modified rows, nothing is binlogged in this # case. So this test is meaningul only in statement-based (and if it was # enabled in row-based, it would fail as expected). -- source include/have_binlog_format_mixed_or_statement.inc source include/master-slave.inc; # see if DROP DATABASE is binlogged even if no effect connection slave; create database mysqltest; connection master; drop database if exists mysqltest; --source include/sync_slave_sql_with_master.inc # can't read dir --replace_result "Errcode: 1" "Errcode: X" "Errcode: 2" "Errcode: X" \\ / --error 1049 show tables from mysqltest; # see if DROP TABLE is binlogged even if no effect connection slave; create table t1 (a int); connection master; drop table if exists t1; --source include/sync_slave_sql_with_master.inc # table does not exist --error 1146 select * from t1; # see if single-table DELETE is binlogged even if no effect connection master; create table t1 (a int, b int); --source include/sync_slave_sql_with_master.inc insert into t1 values(1,1); connection master; delete from t1; --source include/sync_slave_sql_with_master.inc select * from t1; # see if single-table UPDATE is binlogged even if no effect insert into t1 values(1,1); connection master; insert into t1 values(2,1); update t1 set a=2; --source include/sync_slave_sql_with_master.inc select * from t1; # End of 4.1 tests # see if multi-table UPDATE is binlogged even if no effect (BUG#13348) connection master; create table t2 (a int, b int); delete from t1; insert into t1 values(1,1); insert into t2 values(1,1); --source include/sync_slave_sql_with_master.inc # force a difference to see if master's multi-UPDATE will correct it update t1 set a=2; connection master; UPDATE t1, t2 SET t1.a = t2.a; --source include/sync_slave_sql_with_master.inc select * from t1; select * from t2; # See if multi-table DELETE is binlogged even if no effect connection master; delete from t1; delete from t2; --source include/sync_slave_sql_with_master.inc # force a difference to see if master's multi-DELETE will correct it insert into t1 values(1,1); insert into t2 values(1,1); connection master; DELETE t1.*, t2.* from t1, t2; --source include/sync_slave_sql_with_master.inc select * from t1; select * from t2; # cleanup connection master; drop table t1, t2; --source include/sync_slave_sql_with_master.inc --source include/rpl_end.inc