MySQL Bugs: #10799: drop database exists on master cause replication error on slave

Bug #10799	drop database exists on master cause replication error on slave
Submitted:	23 May 2005 10:09	Modified:	23 May 2005 17:52
Reporter:	Sergey Frolovichev	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	4.1.11-standard	OS:	Linux (SuSe Linux 9.3)
Assigned to:		CPU Architecture:	Any

Description:
I have a replication with do-table options.
Just simple drop database on master which doesn't exists on slave, it will cause replication error.

How to repeat:
master - slave replication with do-table options. Create database MUSTBEDROPPED and simply drop it.

What is the error message are you getting?

SQL Running=No last err: Error 'Can't drop database 'Partner3'; database doesn't exist' on query. Default database: ''. Query: 'drop database Partner3'

I was unable to repeat the behavior reported with current server built
from BK source. not error showed after the create database and drop
commands.

     Replicate_Do_Table: dbt.t1
     Replicate_Ignore_Table: 
    Replicate_Wild_Do_Table: 
Replicate_Wild_Ignore_Table: 
                 Last_Errno: 0
                 Last_Error:

This table was in the same database you have created and dropped?
In my case - not the same - replicated tables in Monamour2 and DROPED database which was no on SLAVE was Partner3.
So like this - have Master with:
Monamour2 and Partner3.
After this starting slave with do-table=Monamour2.test
On slave having Monamour2.tes and no Partner3.
Then all i stsarted - cheking replication with executing some queries on Monamour2.test: insert into test (id) values (1);
checking that replication working properly (this record apperiers on slave).
Now making drop database Partner3 on master.

Yes I did and repeated it like you wrote and still can't repeat.