Bug #1093 mysqlbinlog --database does not filter LOAD DATA INFILE
Submitted: 19 Aug 2003 6:04 Modified: 19 Aug 2003 6:52
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[19 Aug 2003 6:04] Guilhem Bichot
When you mysqlbinlog --database=test, and the binlog contains a LOAD DATA INFILE into a table in database test2, this LOAD DATA INFILE is still printed whereas it should be skipped.

How to repeat:
use test2;
create table t(a int);
load data infile 'tmp.txt' into table t;

then mysqlbinlog --database=test, and you still see the LOAD DATA INFILE.

Suggested fix:
will fix it shortly
[19 Aug 2003 6:49] Guilhem Bichot
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

ChangeSet@1.1553.14.1, 2003-08-19 15:12:44+02:00, guilhem@mysql.com
[21 Jul 2009 13:51] Pablo Peranzola
I was having the same problem but i fixed it by "encapsulating" the inner query using an intermediary table (helperTable) 

DELETE from tableOne 
WHERE oid in (SELECT helperTable.oid FROM (SELECT oid FROM tableOne t1 WHERE t1.oid = 5) helperTable);

I hope this solves the issue