11 messages in com.mysql.lists.mysqlReplication| From | Sent On | Attachments |
|---|---|---|
| Jeff Philapy | 12 Jul 2001 14:30 | |
| Jeremy Zawodny | 12 Jul 2001 14:55 | |
| Jeff Philapy | 12 Jul 2001 14:57 | |
| Jeremy Zawodny | 12 Jul 2001 15:08 | |
| Jeff Philapy | 12 Jul 2001 15:48 | |
| Joe Taraba | 12 Jul 2001 16:02 | |
| Brian Reichert | 13 Jul 2001 09:35 | |
| Jeff Philapy | 13 Jul 2001 19:25 | |
| Werner Stuerenburg | 13 Jul 2001 23:37 | |
| Oliver Cook | 17 Jul 2001 05:15 | |
| Jeremy Zawodny | 17 Jul 2001 13:12 |
| Subject: | Replication![]() |
|---|---|
| From: | Oliver Cook (oll...@uk.clara.net) |
| Date: | 07/17/2001 05:15:47 AM |
| List: | com.mysql.lists.mysql |
I saw this in the manual comments on http://www.mysql.com/doc/R/e/Replication_Options.html:
================
: Note that if you client does not do a "USE dbname", binlog-do-db=dbname will
not binlog a query like: "update in dbname.foobar set foo=1" You explicitly have
to do a USE before a query in order to
have your query binlogged, it looks like. Replication on the slave side can do
wildcard matches .. but the master cannot (a la binlog-wild-do-table=dbname.%).
So make sure your clients do a use, if you
plan to replicate those tables it updates.
================
Is this still true in the latest version of MySQL? Is this behaviour by design?
Cheers,
Ollie
-- Oliver Cook Systems Administrator, ClaraNET oll...@uk.clara.net 020 7903 3065




