Bug #7741 no replication with multi-table updates
Submitted: 8 Jan 2005 10:19 Modified: 10 Jan 2005 17:58
Reporter: [ name withheld ] Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0.22 OS:Linux (Red Hat 7.2)
Assigned to: CPU Architecture:Any

[8 Jan 2005 10:19] [ name withheld ]
Description:
Hello,

I found a bug with replication.

UPDATE table SET field='value' WHERE id='123'

=> the UPDATE is replicated

UPDATE table1,table2 SET field='value' WHERE table1.id=table2.id AND table1.id='123'

=> the UPDATE is not replicated

Regards

Olivier Brouckaert

How to repeat:
see above
[8 Jan 2005 10:45] [ name withheld ]
notice : I only use one database
[8 Jan 2005 11:00] [ name withheld ]
to help you, here is the real query

UPDATE forum_msg,forum_msg_txt SET email='user@domaine.com',Message='message' WHERE ID=ID_msg AND ID='123' AND ID_membre='456'

in /etc/my.cnf (master)

log-bin                 = /var/log/mysql/binlog
binlog-do-db            = internet
max_binlog_size         = 100M
server-id               = 1

in /etc/my.cnf (slave)

master-info-file        = /var/log/mysql/master.info
relay-log               = /var/log/mysql/relay
relay-log-index         = /var/log/mysql/relay.index
relay-log-info-file     = /var/log/mysql/relay.info
master-host             = sql.i-services.net
master-user             = repli
master-password         = Rib34chf
master-port             = 3306
master-connect-retry    = 60
server-id               = 2
max-relay-log-size      = 100M
relay-log-space-limit   = 500M
replicate-do-db         = internet
replicate-do-table      = internet.forum_msg
replicate-do-table      = internet.forum_msg_txt
replicate-do-table      = internet.forum_sujet
[10 Jan 2005 11:02] Guilhem Bichot
Thanks much for the bug report! That's the same as http://bugs.mysql.com/bug.php?id=7011 .
[10 Jan 2005 11:18] [ name withheld ]
when this bug will be fixed ?
[10 Jan 2005 17:46] Guilhem Bichot
4.0.23 will probably not be released before several weeks. You can check the progress of BUG#7011.
[10 Jan 2005 17:58] Guilhem Bichot
Sorry, I didn't mean 4.0.23 (which is already released), I meant 4.0.24.