Bug #34 replicate-do-wild-table does not handle drop/create database commands

• Submitted: 17 Jan 2003 11:13
• Modified: 28 Jan 2003 16:56
• Reporter: Peter Zaitsev (Basic Quality Contributor)
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 3.23.x
• OS: Linux (Linux (All?))
• CPU Architecture: Any

[17 Jan 2003 11:13] Peter Zaitsev

Description:
We recommend to use replicate-ignore-wild-table=database.% 
to ignore database from replication,

Thus it does not work completely - create/drop database commands will be still attempted to be replicated which can cause undescirable results.

How to repeat:
1) Create database "repl" on master but not on the slave
2) Setup replication with slave running with --replicate-wild-ignore-table=repl.%
3) run "drop database repl" on the slave

Suggested fix:
Improve the checking so repl.% will  cover database manipulation commands as well.

[28 Jan 2003 16:55] MySQL Developer

Fixed in MySQL 4.0
No changes to 3.23 as this is a behaviour change.