Comment 3 for bug 1074179

Hi Brian,

OK I've worked out what my real issue actually was. It is the way that --empty-replicate-table works. So apparently it empties the table as it checks each table just for that table.

So my workflow was

* run without the ignore
* bad_table now has entries in the checksums table
* run with the ignore
* It still complains because the values aren't deleted from the checksums table

I think the way --empty-replicate-table is non-intuitive. I would expect it to truncate the table so it is always starting afresh so old data can muck up the run.

Cheers,
John