Serious, use a flag in your SQL table model, isDeleted or something, a bit field or boolean. When you do your normal „housecleaning“ (during the nights, while some importan cronjobs are running), you fire a „delete from foobar where isDeleted=true“…you can then avoid having „inserts and deletes“ in your binlog
in the wrong order.

@*8D:
Row based replication can help you here, that’s right, but it can also be a performance killer.
Let’s assume: You have a database with a table of 50mil or more entries…delete from where isDeleted=true, results in a statement based replication in exactly one statement..while in a row based replication it would hit hundreds of thousands of data in your binlog.

The good thing of MySQL 5.1 is, that you can decide what you want to do…mixed mode can help..if you know that deletes should be avoided (This we’re telling as well to our developers, who don’t believe us anyways ;))

Regards,

\sh