Re: Replication without delete
Do you know it could cause synchronisation problem depending to your insert and update pattern?
You may have violate some unique index if the same value is still found in the slave which the rows had been deleted from the master.
Your update may also affect the old rows on the slave which had been deleted from the master, depending to the where condition.
Why don't you move the rows to an archive table instead? And periodically truncate the archive table, and use the 'SET BIN-LOG 0' proposed by Domas when you do the truncate of the archive table.
Subject
Views
Written By
Posted
3768
August 05, 2005 08:22AM
3630
August 23, 2005 12:27AM
Re: Replication without delete
2560
August 23, 2005 07:43PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.